From: Jens Lehmann <Jens.Lehmann@web.de>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org, gitster@pobox.com,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [RFC/PATCH] git-gui: display summary when showing diff of a submodule
Date: Tue, 07 Jul 2009 18:45:38 +0200 [thread overview]
Message-ID: <4A537BB2.90800@web.de> (raw)
In-Reply-To: <4A534728.3050005@drmicha.warpmail.net>
Michael J Gruber schrieb:
> Me wonders whether the summary should be the default diff output, or at
> least a builtin merge driver which can be selected using attributes or such.
Yes, i was thinking about that too. But i have no idea if it would be
a good or bad idea to extend git diff that way.
And for git gui it doesn't really matter. The only difference to my patch
would be the line where the diff command is replaced with submodule summary
(assuming the output would stay compatible). The rest of the patch is about
handling that output, no matter how it is generated.
Jens
prev parent reply other threads:[~2009-07-07 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 21:31 [RFC/PATCH] git-gui: display summary when showing diff of a submodule Jens Lehmann
2009-07-07 13:01 ` Michael J Gruber
2009-07-07 16:45 ` Jens Lehmann [this message]
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=4A537BB2.90800@web.de \
--to=jens.lehmann@web.de \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.org \
/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).