From: John Keeping <john@keeping.me.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Matthieu Moy <Matthieu.Moy@imag.fr>
Subject: [PATCH] fixup! graph: output padding for merge subsequent parents
Date: Sun, 10 Feb 2013 13:16:47 +0000 [thread overview]
Message-ID: <20130210131647.GA2270@serenity.lan> (raw)
In-Reply-To: <7vtxplt5u2.fsf@alter.siamese.dyndns.org>
---
On Sat, Feb 09, 2013 at 03:39:33PM -0800, Junio C Hamano wrote:
> * jk/diff-graph-cleanup (2013-02-07) 6 commits
> - combine-diff.c: teach combined diffs about line prefix
> - diff.c: use diff_line_prefix() where applicable
> - diff: add diff_line_prefix function
> - diff.c: make constant string arguments const
> - diff: write prefix to the correct file
> - graph: output padding for merge subsequent parents
>
> Refactors a lot of repetitive code sequence from the graph drawing
> code and adds it to the combined diff output.
>
> Will merge to 'next'.
Can you squash this into the first commit before you do?
Matthieu is correct that the graph_is_commit_finished() check isn't
needed in the loop now that we've pulled it out to be checked first -
the value returned can't change during the loop. I've left the early
return out.
graph.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/graph.c b/graph.c
index 2a3fc5c..56f970f 100644
--- a/graph.c
+++ b/graph.c
@@ -1237,7 +1237,7 @@ void graph_show_commit(struct git_graph *graph)
shown_commit_line = 1;
}
- while (!shown_commit_line && !graph_is_commit_finished(graph)) {
+ while (!shown_commit_line) {
shown_commit_line = graph_next_line(graph, &msgbuf);
fwrite(msgbuf.buf, sizeof(char), msgbuf.len, stdout);
if (!shown_commit_line)
--
1.8.1.2
next prev parent reply other threads:[~2013-02-10 13:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 23:39 What's cooking in git.git (Feb 2013, #04; Sat, 9) Junio C Hamano
2013-02-10 13:16 ` John Keeping [this message]
2013-02-10 19:30 ` [PATCH] fixup! graph: output padding for merge subsequent parents Junio C Hamano
2013-02-10 21:02 ` John Keeping
2013-02-10 22:38 ` Junio C Hamano
2013-02-11 10:54 ` John Keeping
2013-02-11 16:42 ` Junio C Hamano
2013-02-11 19:06 ` John Keeping
2013-02-11 19:58 ` Junio C Hamano
2013-02-11 9:14 ` What's cooking in git.git (Feb 2013, #04; Sat, 9) Matthieu Moy
2013-02-11 16:01 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130210131647.GA2270@serenity.lan \
--to=john@keeping.me.uk \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).