public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 6.12-rc1
Date: Mon, 30 Sep 2024 21:17:09 +0200	[thread overview]
Message-ID: <Zvr5NRtqxsIwmfeK@zx2c4.com> (raw)
In-Reply-To: <CAHk-=wjm1jLqnMnLar9XRDAwDTHcG7e9+cFhq2bgz4Q+5yysKg@mail.gmail.com>

On Mon, Sep 30, 2024 at 10:22:28AM -0700, Linus Torvalds wrote:
> On Mon, 30 Sept 2024 at 06:15, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> >
> > Pushed 5.12-rc1 too? Odd.
> 
> It's an old tag that was renamed to v5.12-rc1-dontuse when it was
> found to have some particularly nasty problems:
> 
>   https://lore.kernel.org/all/CAHk-=wjnzdLSP3oDxhf9eMTYo7GF-QjaNLBUH1Zk3c4A7X75YA@mail.gmail.com/
> 
> For random reasons (read: I had an old repo) it re-materialized under
> its old name, and because it was *so* co-incidental in naming (getting
> pushed out at the same time as 6.12-rc1), I felt it was too good to
> fix up again.
> 
> And if somebody goes and randomly starts using v5.12-rc1 (from
> February 2021) and hits the swap problem, I can only go "why did you
> do that?"

Ah, I remember that ordeal. I suppose you've been testing out rc1 on
some different hardware and so old repos are found hither and thither.

Jason

  reply	other threads:[~2024-09-30 19:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-29 22:51 Linux 6.12-rc1 Linus Torvalds
2024-09-30  0:38 ` Guenter Roeck
2024-09-30 13:15 ` Jason A. Donenfeld
2024-09-30 17:22   ` Linus Torvalds
2024-09-30 19:17     ` Jason A. Donenfeld [this message]
2024-09-30 14:53 ` Build regressions/improvements in v6.12-rc1 Geert Uytterhoeven
2024-09-30 15:11   ` Geert Uytterhoeven
2024-09-30 16:26     ` Herve Codina
2024-09-30 17:01 ` Linux 6.12-rc1 Guenter Roeck

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=Zvr5NRtqxsIwmfeK@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox