diff options
author | Junio C Hamano <junkio@cox.net> | 2006-03-27 23:58:34 -0800 |
---|---|---|
committer | Junio C Hamano <junkio@cox.net> | 2006-03-28 17:29:21 -0800 |
commit | 384e99a4a99820c34fe3600b2aad3f0185dd43db (patch) | |
tree | 88ff1150dafa6732dd8a6f8a75c59976222910a6 /revision.h | |
parent | 9181ca2c2b1f2897baa67ff8e48b1984822115b5 (diff) | |
download | git-384e99a4a99820c34fe3600b2aad3f0185dd43db.tar.gz |
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>
Diffstat (limited to 'revision.h')
-rw-r--r-- | revision.h | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/revision.h b/revision.h index 6c2becad13..61e6bc9f4b 100644 --- a/revision.h +++ b/revision.h @@ -6,6 +6,7 @@ #define TREECHANGE (1u<<2) #define SHOWN (1u<<3) #define TMP_MARK (1u<<4) /* for isolated cases; clean after use */ +#define BOUNDARY (1u<<5) struct rev_info; @@ -32,7 +33,8 @@ struct rev_info { blob_objects:1, edge_hint:1, limited:1, - unpacked:1; + unpacked:1, + boundary:1; /* special limits */ int max_count; |