From: Krzysztof Kozlowski <krzk@kernel.org>
To: Pavel Machek <pavel@ucw.cz>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: A note on the 5.12-rc1 tag
Date: Thu, 4 Mar 2021 14:23:54 +0100 [thread overview]
Message-ID: <f99457f6-38fb-fd30-da2c-0d5d86e9af39@kernel.org> (raw)
In-Reply-To: <20210304124314.GA9979@duo.ucw.cz>
On 04/03/2021 13:43, Pavel Machek wrote:
>> One additional reason for this note is that I want to not just warn
>> people to not run this if you have a swapfile - even if you are
>> personally not impacted (like I am, and probably most people are -
>> swap partitions all around) - I want to make sure that nobody starts
>> new topic branches using that 5.12-rc1 tag. I know a few developers
>> tend to go "Ok, rc1 is out, I got all my development work into this
>> merge window, I will now fast-forward to rc1 and use that as a base
>> for the next release". Don't do it this time. It may work perfectly
>> well for you because you have the common partition setup, but it can
>> end up being a horrible base for anybody else that might end up
>> bisecting into that area.
>
> Would it make sense to do a -rc2, now, so new topic branches can be
> started on that one?
+1 to this idea. I already applied few patches, well, on top of
v5.12-rc1, so would be nice if I stop this sooner than later.
Best regards,
Krzysztof
next prev parent reply other threads:[~2021-03-04 13:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 20:53 A note on the 5.12-rc1 tag Linus Torvalds
2021-03-04 12:43 ` Pavel Machek
2021-03-04 13:23 ` Krzysztof Kozlowski [this message]
2021-03-04 17:57 ` Linus Torvalds
2021-03-06 12:54 ` Ingo Molnar
2021-03-04 15:00 ` Geert Uytterhoeven
2021-03-04 16:56 ` David Laight
2021-03-04 18:58 ` Geert Uytterhoeven
2021-03-05 9:14 ` David Laight
2021-03-04 20:51 ` Josh Triplett
2021-03-05 5:39 ` Christian Couder
2021-03-05 18:10 ` Junio C Hamano
2021-03-05 23:06 ` Josh Triplett
2021-03-05 23:38 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f99457f6-38fb-fd30-da2c-0d5d86e9af39@kernel.org \
--to=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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 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.