From: Bo Yang <struggleyb.nku@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, trast@student.ethz.ch, peff@peff.net
Subject: [PATCH 0/6 v3] Make git log --graph looks better with -p and other diff options
Date: Thu, 20 May 2010 18:52:38 -0700 [thread overview]
Message-ID: <1274406764-32278-1-git-send-email-struggleyb.nku@gmail.com> (raw)
Thanks to Jeff, make --graph work well with --summary.
And change the call parameters of output_prefix function, remove the unused FILE* and replace it with a diff_options.
Bo Yang (6):
Add a prefix output callback to diff output.
Output the graph columns at the end of the commit message.
diff.c: Output the text graph padding before each diff line.
Emit a whole line once a time.
Register a callback for graph output.
Make --color-words work well with --graph.
color.c | 21 +++-
color.h | 3 +-
diff.c | 379 +++++++++++++++++++++++++++++++++++++++++++++---------------
diff.h | 5 +
graph.c | 19 +++
log-tree.c | 6 +
6 files changed, 331 insertions(+), 102 deletions(-)
next reply other threads:[~2010-05-21 1:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 1:52 Bo Yang [this message]
2010-05-21 1:52 ` [PATCH 1/6 v3] Add a prefix output callback to diff output Bo Yang
2010-05-21 1:52 ` [PATCH 2/6 v3] Output the graph columns at the end of the commit message Bo Yang
2010-05-21 1:52 ` [PATCH 3/6 v3] diff.c: Output the text graph padding before each diff line Bo Yang
2010-05-21 1:52 ` [PATCH 4/6 v3] Emit a whole line once a time Bo Yang
2010-05-21 1:52 ` [PATCH 5/6 v3] Register a callback for graph output Bo Yang
2010-05-21 1:52 ` [PATCH 6/6 v3] Make --color-words work well with --graph Bo Yang
2010-05-21 3:50 ` [PATCH 0/6 v3] Make git log --graph looks better with -p and other diff options Jeff King
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=1274406764-32278-1-git-send-email-struggleyb.nku@gmail.com \
--to=struggleyb.nku@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=trast@student.ethz.ch \
/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).