diff options
| author | Adam Simpkins <adam@adamsimpkins.net> | 2008-05-24 16:02:04 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2008-05-25 12:16:56 -0700 |
| commit | 3c68d67b572bce7ff41de463e75ee093e9dd71b7 (patch) | |
| tree | 644e0db7ea6e4ee7b0a30e50e0b318943a5210fb /revision.c | |
| parent | 7528f27dd677bed65d758667a621034b853595b4 (diff) | |
| download | git-3c68d67b572bce7ff41de463e75ee093e9dd71b7.tar.gz git-3c68d67b572bce7ff41de463e75ee093e9dd71b7.tar.xz | |
Fix output of "git log --graph --boundary"
Previously the graphing API wasn't aware of the revs->boundary flag, and
it always assumed that commits marked UNINTERESTING would not be
displayed. As a result, the boundary commits were printed at the end of
the log output, but they didn't have any branch lines connecting them to
their children in the graph.
There was also another bug in the get_revision() code that caused
graph_update() to be called twice on the first boundary commit. This
caused the graph API to think that a commit had been skipped, and print
a "..." line in the output.
Signed-off-by: Adam Simpkins <adam@adamsimpkins.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'revision.c')
| -rw-r--r-- | revision.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/revision.c b/revision.c index 1341f3d12..181fb0b95 100644 --- a/revision.c +++ b/revision.c @@ -1697,7 +1697,7 @@ static struct commit *get_revision_internal(struct rev_info *revs) * switch to boundary commits output mode. */ revs->boundary = 2; - return get_revision(revs); + return get_revision_internal(revs); } /* |