René Scharfe 49de321698 grep: handle pre context lines on demand
Factor out pre context line handling into the new function
show_pre_context() and change the algorithm to rewind by looking for
newline characters and roll forward again, instead of maintaining an
array of line beginnings and ends.

This is slower for hits, but the cost for non-matching lines becomes
zero.  Normally, there are far more non-matching lines, so the time
spent in total decreases.

Before this patch (current Linux kernel repo, best of five runs):

	$ time git grep --no-ext-grep -B1 memset >/dev/null

	real	0m2.134s
	user	0m1.932s
	sys	0m0.196s

	$ time git grep --no-ext-grep -B1000 memset >/dev/null

	real	0m12.059s
	user	0m11.837s
	sys	0m0.224s

The same with this patch:

	$ time git grep --no-ext-grep -B1 memset >/dev/null

	real	0m2.117s
	user	0m1.892s
	sys	0m0.228s

	$ time git grep --no-ext-grep -B1000 memset >/dev/null

	real	0m2.986s
	user	0m2.696s
	sys	0m0.288s

Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-07-01 19:16:48 -07:00
2009-06-13 12:50:42 -07:00
2009-06-30 16:12:35 -07:00
2009-05-01 22:11:57 -07:00
2009-06-27 13:44:25 -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-06-03 00:49:40 -07:00
2008-08-28 20:50:10 -07:00
2009-03-14 13:36:34 -07:00
2009-05-31 16:57:42 -07:00
2009-04-18 14:45:59 -07:00
2009-05-10 12:41:35 -07:00
2009-02-13 17:27:58 -08:00
2009-05-05 22:49:43 -07:00
2009-06-13 12:48:34 -07:00
2008-10-10 08:39:20 -07:00
2008-10-10 08:39:20 -07:00
2009-05-01 16:07:29 -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-01 19:16:37 -07:00
2008-11-02 16:36:40 -08:00
2009-04-22 19:02:12 -07:00
2009-06-13 12:48:34 -07:00
2008-08-05 21:21:08 -07:00
2009-06-20 21:47:13 -07:00
2008-07-13 14:12:48 -07:00
2009-06-21 21:15:50 -07:00
2008-09-25 08:00:28 -07:00
2008-09-07 23:52:16 -07:00
2009-06-18 10:39:17 -07:00
2009-04-22 19:02:12 -07:00
2009-05-13 20:55:49 -07:00
2009-06-30 16:12:35 -07:00
2008-10-25 12:09:31 -07:00
2009-05-20 00:02:24 -07:00
2009-05-25 19:44:52 -07:00
2009-05-13 20:55:48 -07:00
2009-06-21 21:15:50 -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
2009-06-07 16:23:04 -07:00
2008-03-02 15:11:07 -08:00
2009-01-17 18:30:41 -08:00
2009-06-13 12:53:19 -07:00
2009-04-22 19:02:12 -07:00
2009-04-20 13:44:14 -07:00
2009-02-04 16:30:43 -08:00
2009-02-10 22:26:37 -08: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
No description provided
Readme 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%