From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Gal Paikin <paiking@google.com>,
git@vger.kernel.org, ajp@google.com,
Nasser Grainawi <nasser@codeaurora.org>
Subject: Re: Updating the commit message for reverts
Date: Mon, 30 Dec 2019 21:33:48 +0100 [thread overview]
Message-ID: <20191230203348.GA831634@ugly> (raw)
In-Reply-To: <20191230195915.GE57251@google.com>
On Mon, Dec 30, 2019 at 11:59:15AM -0800, Jonathan Nieder wrote:
>Gal Paikin wrote:
>> The suggestion is to change the behavior to "Revert^N" instead of
>> multiple Reverts one after another.
>
>This would be replacing one kind of jargon with another, so it's not
>clear to me that it would improve matters.
>
>With Revert / Reland, we can forget the N altogether: [...]
>
the irony here is that "reland" is of course yet more jargon. :-D
i'd strongly suggest to use something that actually appears in standard
dictionaries, preferentially "reapply".
> 1. 'Do some great thing'
> 2. 'Revert "Do some great thing"'
> 3. 'Reland "Do some great thing"'
> 4. 'Revert "Do some great thing"'
> 5. (etc)
>
>For the reader of the shortlog, it's not too important how long the
>edit war has gone. The single word makes it clear what the commit
>is going to do.
>
in principle i agree, but it irks me somewhat that the summaries become
non-unique, as that always somewhat impacts history browsing.
prev parent reply other threads:[~2019-12-30 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 11:06 Updating the commit message for reverts Gal Paikin
2019-12-24 19:15 ` Junio C Hamano
2019-12-27 10:13 ` Gal Paikin
2019-12-28 13:20 ` Danh Doan
2019-12-30 16:52 ` Junio C Hamano
2019-12-30 19:55 ` Jonathan Nieder
2019-12-30 19:59 ` Jonathan Nieder
2019-12-30 20:33 ` Oswald Buddenhagen [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=20191230203348.GA831634@ugly \
--to=oswald.buddenhagen@gmx.de \
--cc=ajp@google.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=nasser@codeaurora.org \
--cc=paiking@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.