author | Linus Torvalds <torvalds@ppc970.osdl.org> | |
Mon, 13 Jun 2005 17:06:50 +0000 (10:06 -0700) | ||
committer | Linus Torvalds <torvalds@ppc970.osdl.org> | |
Mon, 13 Jun 2005 17:06:50 +0000 (10:06 -0700) | ||
commit | 178cb243387a24b1dec7613c4c5e97158163ac60 | |
tree | 4ee26dbeb5e1fc42caddbc977e8f282a3f976639 | tree | snapshot |
parent | 84fb9a4dca7efe1427c917e2f46a045e48180826 | commit | diff |
Add 'git-rev-parse' helper script
It's an incredibly cheesy helper that changes human-readable revision
arguments into the git-rev-list argument format.
You can use it to do something like this:
git-rev-list --pretty $(git-rev-parse --default HEAD "$@")
which is what git-log-script will become. Here git-rev-parse will
then allow you to use arguments like "v2.6.12-rc5.." or similar
human-readable ranges.
It's really quite stupid: "a..b" will be converted into "a" and "^b" if
"a" and "b" are valid object pointers. And the "--default" case will be
used if nothing but flags have been seen, so that you can default to a
certain argument if there are no other ranges.
It's an incredibly cheesy helper that changes human-readable revision
arguments into the git-rev-list argument format.
You can use it to do something like this:
git-rev-list --pretty $(git-rev-parse --default HEAD "$@")
which is what git-log-script will become. Here git-rev-parse will
then allow you to use arguments like "v2.6.12-rc5.." or similar
human-readable ranges.
It's really quite stupid: "a..b" will be converted into "a" and "^b" if
"a" and "b" are valid object pointers. And the "--default" case will be
used if nothing but flags have been seen, so that you can default to a
certain argument if there are no other ranges.
Makefile | diff | blob | history | |
rev-parse.c | [new file with mode: 0644] | blob |