From: Paul Mackerras <paulus@samba.org>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] gitk: Use the --submodule option for diffs
Date: Wed, 28 Oct 2009 15:03:20 +1100 [thread overview]
Message-ID: <19175.49800.697048.349753@drongo.ozlabs.ibm.com> (raw)
In-Reply-To: <4AE70AC9.6040302@web.de>
Jens Lehmann writes:
> Instead of just showing not-quite-helpful SHA-1 pairs display the first
> lines of the corresponding commit messages in the submodule (similar to
> the output of 'git submodule summary').
>
> Signed-off-by: Jens Lehmann <Jens.Lehmann@web.de>
> ---
>
> This patch applies to 'next' and uses the new --submodule option of git
> diff to achieve a more meaningful output of submodule differences in
> gitk.
(That sentence should have been in the commit message.)
> Any objections against making this the default?
What version of git is the first to have the --submodule option?
Since it's a new option we should make gitk use it only if the
underlying git is new enough, like we do with the --textconv option.
Also, the commit message is a bit sparse; it doesn't mention that this
affects the diff display, for instance.
Paul.
next prev parent reply other threads:[~2009-10-28 4:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 14:59 [PATCH] gitk: Use the --submodule option for diffs Jens Lehmann
2009-10-27 15:41 ` Johannes Schindelin
2009-10-28 4:03 ` Paul Mackerras [this message]
2009-10-28 11:40 ` [PATCH v2] gitk: Use the --submodule option for displaying diffs when available Jens Lehmann
2009-11-03 11:32 ` Paul Mackerras
2009-10-28 7:19 ` [PATCH] gitk: Use the --submodule option for diffs 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=19175.49800.697048.349753@drongo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=Jens.Lehmann@web.de \
--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).