git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: git@vger.kernel.org
Subject: Re: [PATCH] sequencer: beautify subject of reverts of reverts
Date: Tue, 28 Mar 2023 15:23:58 +0200	[thread overview]
Message-ID: <ZCLqbmWsN/7Ihjg+@ugly> (raw)
In-Reply-To: <4f570b05-036d-45a1-8caa-cebfce3026c9@app.fastmail.com>

On Tue, Mar 28, 2023 at 08:04:43AM +0200, Kristoffer Haugsbakk wrote:
>On Tue, Mar 28, 2023, at 00:25, Junio C Hamano wrote:
>> ""Revert^4 "A change" the other thread proposed start to look less horrible.
>> So, I dunno.
>
>That looks good. And the transformations are just:
>
>    Revert " → Reapply "
>    Reapply " → Revert^3 "
>    Revert^<n> " → Revert^<n+1> "
>
i thought about that already, and concluded that it's getting a bit "too 
nerdy" and over-engineered.
the main motivation for me is to break the dogmatism with which some 
people are approaching the matter - "$tool did it, so it is _the_ way".  
set an example where the tool does something "humane", and you may 
change some minds.
when it gets to round 3 of reverting, i expect people to get creative:

  Revert "foo" again
  Reapply "foo", take 2
  etc.

but i don't mind, as long as `Revert "Revert "Revert "foo"""` cannot be 
argued to be canon any more.

  reply	other threads:[~2023-03-28 13:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 16:22 [PATCH] sequencer: beautify subject of reverts of reverts Oswald Buddenhagen
2023-03-25 10:39 ` Kristoffer Haugsbakk
2023-03-27 22:25   ` Junio C Hamano
2023-03-28  6:04     ` Kristoffer Haugsbakk
2023-03-28 13:23       ` Oswald Buddenhagen [this message]
2023-03-28 13:43         ` Kristoffer Haugsbakk
2023-03-28 14:00         ` Junio C Hamano
2023-03-28 14:02 ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZCLqbmWsN/7Ihjg+@ugly \
    --to=oswald.buddenhagen@gmx.de \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).