author | Junio C Hamano <junkio@cox.net> | |
Tue, 28 Mar 2006 07:58:34 +0000 (23:58 -0800) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Wed, 29 Mar 2006 01:29:21 +0000 (17:29 -0800) | ||
commit | 384e99a4a99820c34fe3600b2aad3f0185dd43db | |
tree | 88ff1150dafa6732dd8a6f8a75c59976222910a6 | tree | snapshot |
parent | 9181ca2c2b1f2897baa67ff8e48b1984822115b5 | commit | diff |
rev-list --boundary
With the new --boundary flag, the output from rev-list includes
the UNINTERESING commits at the boundary, which are usually not
shown. Their object names are prefixed with '-'.
For example, with this graph:
C side
/
A---B---D master
You would get something like this:
$ git rev-list --boundary --header --parents side..master
D B
tree D^{tree}
parent B
... log message for commit D here ...
\0-B A
tree B^{tree}
parent A
... log message for commit B here ...
\0
Signed-off-by: Junio C Hamano <junkio@cox.net>
With the new --boundary flag, the output from rev-list includes
the UNINTERESING commits at the boundary, which are usually not
shown. Their object names are prefixed with '-'.
For example, with this graph:
C side
/
A---B---D master
You would get something like this:
$ git rev-list --boundary --header --parents side..master
D B
tree D^{tree}
parent B
... log message for commit D here ...
\0-B A
tree B^{tree}
parent A
... log message for commit B here ...
\0
Signed-off-by: Junio C Hamano <junkio@cox.net>
rev-list.c | diff | blob | history | |
revision.c | diff | blob | history | |
revision.h | diff | blob | history |