From: Jeff King <peff@peff.net>
To: Patrick Steinhardt <ps@pks.im>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.34.0-rc2
Date: Mon, 15 Nov 2021 10:27:36 -0500 [thread overview]
Message-ID: <YZJ8aDNVentnbalp@coredump.intra.peff.net> (raw)
In-Reply-To: <YZJ3hZkX9YjNBAdk@ncase>
On Mon, Nov 15, 2021 at 04:06:45PM +0100, Patrick Steinhardt wrote:
> Sorry, but I'm currently completely loaded with work and thus didn't
> find the capacity to have a deeper look yet and will probably not find
> the time for a few more days. So the earliest I can have a look at this
> is probably beginning next week.
>
> With that in mind, I'm happy to have this change reverted for now, as it
> is...
Thanks for chiming in (and again, sorry for bringing this up so late in
the cycle).
> > > We probably should revert this step as it can affect correctness in
> > > a big way, but I wonder if the other steps in the same series, or
> > > other topic that came later, rely on it.
> >
> > I looked them over, and I think this is pretty independent (with the
> > exception of the refactoring of the no_walk/unsorted flags, but
> > obviously that had to come first).
>
> .. completely independent of the other patches in this series and can be
> reverted on its own. Only question is whether we also want to revert the
> patch introducing this option in the first place given that it would end
> up without a user afterwards.
It looks like Junio queued a revert of the whole patch in a7df4f52af
(Revert "connected: do not sort input revisions", 2021-11-11), which is
on "master". So I think we should have a clean slate to look at this in
the next cycle.
-Peff
next prev parent reply other threads:[~2021-11-15 15:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 0:59 [ANNOUNCE] Git v2.34.0-rc2 Junio C Hamano
2021-11-10 5:41 ` Jeff King
2021-11-10 6:00 ` Jeff King
2021-11-10 8:11 ` Carlo Arenas
2021-11-10 8:22 ` Jeff King
2021-11-10 9:15 ` Carlo Arenas
2021-11-10 9:35 ` Jeff King
2021-11-10 9:39 ` [PATCH] RelNotes: mention known crasher when ssh signing with OpenSSH 8.7 Carlo Marcelo Arenas Belón
2021-11-10 21:39 ` Junio C Hamano
2021-11-10 22:11 ` Junio C Hamano
2021-11-11 9:16 ` Jeff King
[not found] ` <YY7/peK1EOHtATEI@camp.crustytoothpaste.net>
2021-11-13 0:16 ` Junio C Hamano
2021-11-10 21:49 ` [ANNOUNCE] Git v2.34.0-rc2 Junio C Hamano
2021-11-10 6:35 ` Johannes Altmanninger
2021-11-10 8:22 ` Jeff King
2021-11-10 21:43 ` Junio C Hamano
2021-11-11 12:07 ` Jeff King
2021-11-11 17:32 ` Junio C Hamano
2021-11-11 20:23 ` Jeff King
2021-11-11 20:33 ` Junio C Hamano
2021-11-15 15:06 ` Patrick Steinhardt
2021-11-15 15:27 ` Jeff King [this message]
2021-11-15 16:52 ` Jeff King
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=YZJ8aDNVentnbalp@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/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).