From: Michael J Gruber <git@drmicha•warpmail.net>
To: Jens Lehmann <Jens.Lehmann@web•de>
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 15:01:28 +0200 [thread overview]
Message-ID: <4A534728.3050005@drmicha.warpmail.net> (raw)
In-Reply-To: <4A526D15.3090202@web.de>
Jens Lehmann venit, vidit, dixit 06.07.2009 23:31:
> As it is hard to say what changed in a submodule by looking at the hashes,
> let's show the colored submodule summary instead.
>
I can't comment on the patch but I find the goal very valid. I just
updated the submodule tutorial wiki to use "git submodule summary" in
addition to plain diff.
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.
Michael
next prev parent reply other threads:[~2009-07-07 13:01 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 [this message]
2009-07-07 16:45 ` Jens Lehmann
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=4A534728.3050005@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=Jens.Lehmann@web$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=spearce@spearce$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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