aboutsummaryrefslogtreecommitdiff
path: root/revision.h
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2006-04-16 18:12:49 -0700
committerJunio C Hamano <junkio@cox.net>2006-04-16 22:05:38 -0700
commit1b65a5aa449e2ea99a68f5d13c5521d0dc64dfd1 (patch)
tree4a9db3b92e5e94addafb6e6120015622476dbd85 /revision.h
parente6bfaf3e33beba9431490a4f5c7a9753986554c4 (diff)
downloadgit-1b65a5aa449e2ea99a68f5d13c5521d0dc64dfd1.tar.gz
git-1b65a5aa449e2ea99a68f5d13c5521d0dc64dfd1.tar.xz
rev-list --boundary: show boundary commits even when limited otherwise.
The boundary commits are shown for UI like gitk to draw them as soon as topo-order sorting allows, and should not be omitted by get_revision() filtering logic. As long as their immediate child commits are shown, we should not filter them out. Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'revision.h')
-rw-r--r--revision.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/revision.h b/revision.h
index 8970b57e3..4b2704351 100644
--- a/revision.h
+++ b/revision.h
@@ -7,7 +7,8 @@
#define SHOWN (1u<<3)
#define TMP_MARK (1u<<4) /* for isolated cases; clean after use */
#define BOUNDARY (1u<<5)
-#define ADDED (1u<<6) /* Parents already parsed and added? */
+#define BOUNDARY_SHOW (1u<<6)
+#define ADDED (1u<<7) /* Parents already parsed and added? */
struct rev_info;