From: Thomas Rast <trast@student.ethz.ch>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Björn Steinbrink" <B.Steinbrink@gmx.de>,
"Abhijit Menon-Sen" <ams@toroid.org>
Subject: Re: [PATCH] Make 'diff C^!' show the same diff as 'show C'
Date: Fri, 21 Aug 2009 00:42:03 +0200 [thread overview]
Message-ID: <200908210042.05802.trast@student.ethz.ch> (raw)
In-Reply-To: <7vab1up1gz.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Thomas Rast <trast@student.ethz.ch> writes:
>
> > Ideally, we'd like 'git diff C^!' to show the same diff that 'git show C'
> > does (with log.showroot enabled). This gives easy access to a readable
> > diff for the commit, irrespective of how many parents it has and without
> > any trickery to remove the commit message from the git-show output.
>
> Not interested yet, as the "git show" discussion is not convincing at all.
Well, it is currently half-supported, diff doesn't complain about it,
yet it does something wildly different from what people expect in the
zero- and two-parent cases.
And yes, people expect this to work; searching the #git logs (I won't
link here as it takes a fair while even for one request) shows that
people such as Dscho, Thiago, Jakub and Björn have recommended this
syntax in the context of diff.
> Is the message annoying enough to warrant this change?
>
> If that is indeed the case and if it is a common thing to ask, isn't it
> more productive to teach "show" a way to do so in a simpler way than
> doing, say,
>
> $ git show --pretty=format: HEAD
That still doesn't get rid of the stray newline.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2009-08-20 22:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 22:10 [PATCH] Make 'diff C^!' show the same diff as 'show C' Thomas Rast
2009-08-20 22:25 ` Junio C Hamano
2009-08-20 22:34 ` Jeff King
2009-08-20 23:01 ` Junio C Hamano
2009-08-20 22:42 ` Thomas Rast [this message]
2009-08-20 23:03 ` Junio C Hamano
2009-08-20 23:31 ` Junio C Hamano
2009-08-20 23:35 ` 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=200908210042.05802.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=B.Steinbrink@gmx.de \
--cc=ams@toroid.org \
--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