1
0
mirror of https://github.com/git/git.git synced 2025-03-19 22:48:44 +00:00
Junio C Hamano a26345b608 grep: optimize built-in grep by skipping lines that do not hit
The internal "grep" engine we use checks for hits line-by-line, instead of
letting the underlying regexec()/fixmatch() routines scan for the first
match from the rest of the buffer.  This was a major source of overhead
compared to the external grep.

Introduce a "look-ahead" mechanism to find the next line that would
potentially match by using regexec()/fixmatch() in the remainder of the
text to skip unmatching lines, and use it when the query criteria is
simple enough (i.e. punt for an advanced grep boolean expression like
"lines that have both X and Y but not Z" for now) and we are not running
under "-v" (aka "--invert-match") option.

Note that "-L" (aka "--files-without-match") is not a reason to disable
this optimization.  Under the option, we are interested if the file has
any hit at all, and that is what we determine reliably with or without the
optimization.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-01-12 00:47:50 -08:00
2009-09-16 14:53:26 -07:00
2009-05-01 22:11:57 -07:00
2009-05-23 01:39:15 -07:00
2009-04-17 21:42:12 -07:00
2008-07-19 11:25:51 -07:00
2008-07-19 11:17:43 -07:00
2009-05-25 01:07:25 -07:00
2009-06-30 16:12:24 -07:00
2009-04-17 21:05:49 -07:00
2009-06-18 09:22:46 -07:00
2009-07-24 09:27:09 -07:00
2008-08-28 20:50:10 -07:00
2009-03-14 13:36:34 -07:00
2009-07-06 09:39:46 -07:00
2009-07-06 09:39:46 -07:00
2009-07-06 09:39:46 -07:00
2009-05-10 12:41:35 -07:00
2009-02-13 17:27:58 -08:00
2009-07-22 21:56:46 -07:00
2009-08-10 14:39:39 -07:00
2009-08-05 12:37:24 -07:00
2008-10-10 08:39:20 -07:00
2009-05-01 16:07:29 -07:00
2009-07-06 09:39:46 -07:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2009-06-20 21:47:30 -07:00
2009-07-09 00:59:58 -07:00
2008-11-02 16:36:40 -08:00
2009-04-22 19:02:12 -07:00
2008-08-05 21:21:08 -07:00
2008-07-13 14:12:48 -07:00
2009-09-16 14:53:26 -07:00
2008-09-25 08:00:28 -07:00
2009-08-12 16:15:55 -07:00
2008-09-07 23:52:16 -07:00
2009-07-06 09:39:46 -07:00
2009-04-22 19:02:12 -07:00
2009-07-06 09:39:46 -07:00
2009-07-24 09:27:09 -07:00
2008-10-25 12:09:31 -07:00
2009-05-20 00:02:24 -07:00
2009-05-13 20:55:48 -07:00
2009-09-16 14:53:26 -07:00
2009-06-20 21:47:27 -07:00
2009-02-14 21:27:35 -08:00
2008-07-21 19:11:50 -07:00
2009-04-22 19:02:12 -07:00
2008-03-02 15:11:07 -08:00
2009-01-17 18:30:41 -08:00
2009-04-20 13:44:14 -07:00
2009-07-18 16:57:47 -07:00
2009-02-04 16:30:43 -08:00
2009-07-22 21:57:41 -07:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

Git is a fast, scalable, distributed revision control system with an
unusually rich command set that provides both high-level operations
and full access to internals.

Git is an Open Source project covered by the GNU General Public License.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.

See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.txt for documentation of each command.
If git has been correctly installed, then the tutorial can also be
read with "man gittutorial" or "git help tutorial", and the
documentation of each command with "man git-commandname" or "git help
commandname".

CVS users may also want to read Documentation/gitcvs-migration.txt
("man gitcvs-migration" or "git help cvs-migration" if git is
installed).

Many Git online resources are accessible from http://git.or.cz/
including full documentation and Git related tools.

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to git@vger.kernel.org. To subscribe
to the list, send an email with just "subscribe git" in the body to
majordomo@vger.kernel.org. The mailing list archives are available at
http://marc.theaimsgroup.com/?l=git and other archival sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 794 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%