Junio C Hamano gits...@pobox.com writes:
Also I wonder if this one Documentation/git-log.txt:156
git log -L '/int main/',/^}/:main.c
should be more like one of these:
git log -L '/int main/,/^}/':main.c
git log -L '/int main/,/^}/:main.c'
I find it somewhat hard to spot the
Thomas Rast tr...@inf.ethz.ch writes:
Junio C Hamano gits...@pobox.com writes:
Also I wonder if this one Documentation/git-log.txt:156
git log -L '/int main/',/^}/:main.c
should be more like one of these:
git log -L '/int main/,/^}/':main.c
git log -L '/int
Eric Sunshine sunsh...@sunshineco.com writes:
Standard practice in Git documentation is for each variation of an
option (such as: -p / --porcelain) to be placed on its own line in the
OPTIONS table. The -L option does not follow suit. It cuddles
-L start,end and -L :regex, separated by a
Thomas Rast t...@thomasrast.ch writes:
Eric Sunshine sunsh...@sunshineco.com writes:
Standard practice in Git documentation is for each variation of an
option (such as: -p / --porcelain) to be placed on its own line in the
OPTIONS table. The -L option does not follow suit. It cuddles
-L
Standard practice in Git documentation is for each variation of an
option (such as: -p / --porcelain) to be placed on its own line in the
OPTIONS table. The -L option does not follow suit. It cuddles
-L start,end and -L :regex, separated by a comma. This is
inconsistent and potentially confusing
5 matches
Mail list logo
