From: Junio C Hamano Date: Mon, 17 Apr 2006 01:53:43 GMT Subject: [PATCH] rev-list --boundary: show boundary commits even when limited otherwise. Message-ID: <7vy7y5nf14.fsf_-_@assigned-by-dhcp.cox.net> In-Reply-To: <7vslodp4sk.fsf@assigned-by-dhcp.cox.net> 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 --- > The real issue is "git-rev-list --boundary ran..ge -- path" does > not show boundary. I am not sure if it even worked in the past; > will take a look. I _think_ this fixes it, but this is rev-list which I feel a bit uneasy touching. A lower-impact approach of not filtering BOUNDARY commits at all does not work well; it shows many isolated open-circle commits in gitk that do not touch the specified paths. I got tired of updating the private object.flags users, so just reserved the lower 16 bits for use of revision.c while I was at it. http-push.c | 10 +++++----- rev-list.c | 4 ++-- revision.c | 29 +++++++++++++++++++++++++++-- revision.h | 3 ++- 4 files changed, 36 insertions(+), 10 deletions(-) 298196646f35b6f5bc2131074204826d39aff8cf diff --git a/http-push.c b/http-push.c index 19a0f77..e7f7f44 100644 --- a/http-push.c +++ b/http-push.c @@ -60,12 +60,12 @@ #define LOCK_REQUEST "... [ -- paths... ]\n" diff --git a/revision.c b/revision.c index 0505f3f..e1f9816 100644 --- a/revision.c +++ b/revision.c @@ -750,6 +750,17 @@ static void rewrite_parents(struct rev_i } } +static void mark_boundary_to_show(struct commit *commit) +{ + struct commit_list *p = commit->parents; + while (p) { + commit = p->item; + p = p->next; + if (commit->object.flags & BOUNDARY) + commit->object.flags |= BOUNDARY_SHOW; + } +} + struct commit *get_revision(struct rev_info *revs) { struct commit_list *list = revs->commits; @@ -787,8 +798,20 @@ struct commit *get_revision(struct rev_i } if (commit->object.flags & SHOWN) continue; - if (!(commit->object.flags & BOUNDARY) && - (commit->object.flags & UNINTERESTING)) + + /* We want to show boundary commits only when their + * children are shown. When path-limiter is in effect, + * rewrite_parents() drops some commits from getting shown, + * and there is no point showing boundary parents that + * are not shown. After rewrite_parents() rewrites the + * parents of a commit that is shown, we mark the boundary + * parents with BOUNDARY_SHOW. + */ + if (commit->object.flags & BOUNDARY_SHOW) { + commit->object.flags |= SHOWN; + return commit; + } + if (commit->object.flags & UNINTERESTING) continue; if (revs->min_age != -1 && (commit->date > revs->min_age)) continue; @@ -801,6 +824,8 @@ struct commit *get_revision(struct rev_i if (revs->parents) rewrite_parents(revs, commit); } + if (revs->boundary) + mark_boundary_to_show(commit); commit->object.flags |= SHOWN; return commit; } while (revs->commits); diff --git a/revision.h b/revision.h index 8970b57..4b27043 100644 --- a/revision.h +++ b/revision.h @@ -7,7 +7,8 @@ #define TREECHANGE (1u<<2) #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; -- 1.3.0.rc4.g878b