From: "Björn Gustavsson" <bgustavsson@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Stephen Boyd <bebarino@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH bg/format-patch-p-noop] log-tree: always add --- marker when options are patch and a stat
Date: Wed, 4 Nov 2009 08:00:58 +0100 [thread overview]
Message-ID: <6672d0160911032300w1a2dfdbck5b1db98f2059639b@mail.gmail.com> (raw)
In-Reply-To: <7vy6mmltz9.fsf@alter.siamese.dyndns.org>
2009/11/4 Junio C Hamano <gitster@pobox.com>:
> In an ideal world, I would probably say:
>
> * format-patch should have three-dash after the commit message, no matter
> what format the patch is asked for, and it always will give patch text.
I agree.
> * format-patch -p should be reinstated as a way to ask for "just patch
> text, no diffstat". Introducing a new option --no-stat _in addition_
> to improve the UI is Ok.
Since -p has been broken for 14 months, is really necessary to reinstate
it? (Or has the breakage not been reported because the people who care
still use a git version older than 14 months?)
Why not just add a new --no-stat option?
> * format-patch -U<n> should not be mistaken as a request to suppress
> diffstat; what 68daa64 _tried_ to do was worthy.
I agree.
/Björn
--
Björn Gustavsson, Erlang/OTP, Ericsson AB
next prev parent reply other threads:[~2009-11-04 7:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 21:24 [PATCH bg/format-patch-p-noop] log-tree: always add --- marker when options are patch and a stat Stephen Boyd
2009-11-04 5:49 ` Junio C Hamano
2009-11-04 6:36 ` Jeff King
2009-11-04 7:10 ` Jeff King
2009-11-04 7:19 ` Jeff King
2009-11-04 7:35 ` Stephen Boyd
2009-11-04 7:37 ` Jeff King
2009-11-04 18:10 ` Junio C Hamano
2009-11-04 7:49 ` Björn Gustavsson
2009-11-04 7:26 ` Junio C Hamano
2009-11-04 7:00 ` Björn Gustavsson [this message]
2009-11-04 7:31 ` 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=6672d0160911032300w1a2dfdbck5b1db98f2059639b@mail.gmail.com \
--to=bgustavsson@gmail.com \
--cc=bebarino@gmail.com \
--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).