git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: phillip.wood@dunelm.org.uk,
	Phillip Wood via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org,
	Jonas Kittner <jonas.kittner@ruhr-uni-bochum.de>
Subject: Re: [PATCH] rebase -i: fix rewording with --committer-date-is-author-date
Date: Wed, 03 Nov 2021 23:27:28 -0700	[thread overview]
Message-ID: <xmqq4k8s4er3.fsf@gitster.g> (raw)
In-Reply-To: <YYM/bm7cHpJeJoGT@coredump.intra.peff.net> (Jeff King's message of "Wed, 3 Nov 2021 22:03:26 -0400")

Jeff King <peff@peff.net> writes:

> ... I just didn't
> consider it quite the same as a bug that had never been in a released
> version at all (and I know you are often hesitant to throw too much into
> the -rc part of the cycle).

Ah, I see.

2.33.1 was 2.33.0 plus what was queued on 'master' back then for
2.34.0, and more importantly, we do not issue the maintenance track
very often these days (except for occasional security patches).

To put it differently, I didn't have to issue 2.33.1. There was
nothing urgent in there, and it was just that the cycle toward 2.34
was unusually busy and there were too many accumulated fixes on the
'master' front that were 'maint' material.  And for that reason, in
my mind, 2.33.1 cannot be treated quite the same way as feature
releases X.YY.0, when I say "The bug was already present in that
released version, so fixing it is not all that urgent".

      reply	other threads:[~2021-11-04  6:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 20:10 [PATCH] rebase -i: fix rewording with --committer-date-is-author-date Phillip Wood via GitGitGadget
2021-11-02 21:05 ` Eric Sunshine
2021-11-02 21:29   ` Phillip Wood
2021-11-02 21:30 ` [PATCH v2] " Phillip Wood via GitGitGadget
2021-11-02 22:32 ` [PATCH] " Jeff King
2021-11-03 11:23   ` Phillip Wood
2021-11-03 11:42     ` Jeff King
2021-11-03 17:44       ` Junio C Hamano
2021-11-04  2:03         ` Jeff King
2021-11-04  6:27           ` Junio C Hamano [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=xmqq4k8s4er3.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=jonas.kittner@ruhr-uni-bochum.de \
    --cc=peff@peff.net \
    --cc=phillip.wood@dunelm.org.uk \
    /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).