From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <gitster@pobox.com>
Cc: Dan Johnson <computerdruid@gmail.com>,
Peter Jones <pjones@redhat.com>,
git@vger.kernel.org
Subject: Re: [PATCH] git-am: Handle "git show" output correctly
Date: Thu, 13 Sep 2012 00:41:00 +0200 [thread overview]
Message-ID: <50510F7C.4080700@op5.se> (raw)
In-Reply-To: <7vhar2c29s.fsf@alter.siamese.dyndns.org>
On 09/13/2012 12:19 AM, Junio C Hamano wrote:
> Dan Johnson <computerdruid@gmail.com> writes:
>
>>> Not really. If we start encouraging people to use "git show" output
>>> as a kosher input to "am", we would have to support such use
>>> forever, and we end up painting ourselves in a corner we cannot get
>>> out of easily.
>>
>> If git am emitted a warning when accepting "git show" output, it seems
>> like it would support Peter's use-case without encouraging bad
>> behavior?
>
> Are you seriously suggesting me to sell to our users a new feature
> saying "this does not work reliably, we would not recommend using
> it, no, really, don't trust it." from the day the feature is
> introduced, especially when we know it will not be "the feature does
> not work well yet, but it will, we promise" but is "and it may become
> worse in the future"?
>
> I do not see much point in doing that.
>
> Besides, what bad behaviour do we avoid from encouraging with such
> an approach? As Peter said, the problem is not on the part of the
> user who ended up with an output from "git show", when he really
> wants output from "git format-patch". Giving the warning to the
> user of "git am" is too late.
>
It might be enough to either enable format-patch output or print a
warning to stderr when stdout is not a tty. I believe that would at
least mitigate the problem, and it might educate the user as well.
We already modify output format when stdout is not a tty (removing
colors), so we're not giving guarantees about its format when it's
piped somewhere. I believe that would provide almost every scenario
with the expected outcome (including 'git show | grep'), but there
will be a handful of very surprised people as well.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
prev parent reply other threads:[~2012-09-12 22:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 15:26 [PATCH] Handle "git show" output correctly Peter Jones
2012-09-12 15:30 ` Peter Jones
2012-09-12 15:41 ` Matthieu Moy
2012-09-12 15:49 ` [PATCH] [git-am] " Peter Jones
2012-09-12 15:57 ` Matthieu Moy
2012-09-12 17:32 ` Junio C Hamano
2012-09-12 18:05 ` Peter Jones
2012-09-12 19:07 ` Junio C Hamano
2012-09-12 15:42 ` [PATCH] " Peter Jones
2012-09-12 15:40 ` Matthieu Moy
2012-09-12 18:00 ` Peter Jones
2012-09-12 18:08 ` [PATCH] git-am: " Peter Jones
2012-09-12 20:06 ` Junio C Hamano
2012-09-12 20:48 ` Peter Jones
2012-09-12 21:03 ` Peter Jones
2012-09-12 21:18 ` Junio C Hamano
2012-09-12 21:26 ` Dan Johnson
2012-09-12 22:19 ` Junio C Hamano
2012-09-12 22:31 ` Dan Johnson
2012-09-12 23:05 ` Junio C Hamano
2012-09-12 22:41 ` Andreas Ericsson [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=50510F7C.4080700@op5.se \
--to=ae@op5.se \
--cc=computerdruid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pjones@redhat.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).