diff options
author | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-06-04 14:38:28 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-06-04 14:38:28 -0700 |
commit | 337cb3fb8da45f10fe9a0c3cf571600f55ead2ce (patch) | |
tree | a0b72bf6b71119b47b65072ef45592f69749a07d /git-shortlog | |
parent | dba385bb3ed541c4d18e2b8080960eee358394fa (diff) | |
download | git-337cb3fb8da45f10fe9a0c3cf571600f55ead2ce.tar.gz git-337cb3fb8da45f10fe9a0c3cf571600f55ead2ce.tar.xz |
git-rev-list: allow arbitrary head selections, use git-rev-tree syntax
This makes git-rev-list use the same command line syntax to mark the
commits as git-rev-tree does, and instead of just allowing a start and
end commit, it allows an arbitrary list of "interesting" and "uninteresting"
commits.
For example, imagine that you had three branches (a, b and c) that you
are interested in, but you don't want to see stuff that already exists
in another persons three releases (x, y and z). You can do
git-rev-list a b c ^x ^y ^z
(order doesn't matter, btw - feel free to put the uninteresting ones
first or otherwise swithc them around), and it will show all the
commits that are reachable from a/b/c but not reachable from x/y/z.
The old syntax "git-rev-list start end" would not be written as
"git-rev-list start ^end", or "git-rev-list ^end start".
There's no limit to the number of heads you can specify (unlike
git-rev-tree, which can handle a maximum of 16 heads).
Diffstat (limited to 'git-shortlog')
0 files changed, 0 insertions, 0 deletions