kernel/git - git - PowerEL Git System

Tree: fa21b60232

Author	SHA1	Message	Date
Junio C Hamano	2c866cf1c2	builtin-grep: support -c (--count). Signed-off-by: Junio C Hamano <junkio@cox.net>	19 years ago
Junio C Hamano	f9b9faf6f8	builtin-grep: allow more than one patterns. Signed-off-by: Junio C Hamano <junkio@cox.net>	19 years ago
Junio C Hamano	f462ebb48b	builtin-grep: allow -<n> and -[ABC]<n> notation for context lines. Signed-off-by: Junio C Hamano <junkio@cox.net>	19 years ago
Junio C Hamano	a24f1e254e	builtin-grep: printf %.*s length is int, not ptrdiff_t. Signed-off-by: Junio C Hamano <junkio@cox.net>	19 years ago
Junio C Hamano	1362671f6a	builtin-grep: do not use setup_revisions() Grep may want to grok multiple revisions, but it does not make much sense to walk revisions while doing so. This stops calling the code to parse parameters for the revision walker. The parameter parsing for the optional "-e" option becomes a lot simpler with it as well. Signed-off-by: Junio C Hamano <junkio@cox.net>	19 years ago
Junio C Hamano	df0e7aa864	builtin-grep: support '-l' option. Signed-off-by: Junio C Hamano <junkio@cox.net>	19 years ago
Junio C Hamano	e0eb889f8e	builtin-grep: wildcard pathspec fixes This tweaks the pathspec wildcard used in builtin-grep to match that of ls-files. With this: git grep -e DEBUG -- '/Kconfig' would work like the shell script version, and you could even do: git grep -e DEBUG --cached -- '/Kconfig' ;# from index git grep -e DEBUG v2.6.12 -- '/Kconfig' ;# from rev Signed-off-by: Junio C Hamano <junkio@cox.net>	19 years ago
Junio C Hamano	5010cb5fcc	built-in "git grep" This attempts to set up built-in "git grep" to further reduce our dependence on the shell, while at the same time optionally allowing to run grep against object database. You could do funky things like these: git grep --cached -e pattern ;# grep from index git grep -e pattern master ;# or in a rev git grep -e pattern master next ;# or in multiple revs git grep -e pattern pu^@ ;# even like this with an ;# extension from another topic ;-) git grep -e pattern master..next ;# or even from rev ranges git grep -e pattern master~20:Documentation ;# or an arbitrary tree git grep -e pattern next:git-commit.sh ;# or an arbitrary blob Right now, it does not understand and/or obey many options grep should accept, and the pattern must be given with -e option due to the way the parameter parser is structured, both of which obviously need to be fixed for usability. But this is going in the right direction. The shell script version is one of the worst Portability offender in the git barebone Porcelainish; it uses xargs -0 to pass paths around and shell arrays to sift flags and parameters. Signed-off-by: Junio C Hamano <junkio@cox.net>	19 years ago

1 2