All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org,
	 Kalle Valo <kvalo@kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	fw@strlen.de,  pablo@netfilter.org, bpf@vger.kernel.org
Subject: Re: [ANN] Winter break shutdown plan
Date: Thu, 21 Dec 2023 10:09:45 -0800	[thread overview]
Message-ID: <CAHk-=whceLbGZwuLnR0S3V_ajedDXj=s86sm89m+VT2YrbG1NA@mail.gmail.com> (raw)
In-Reply-To: <20231205101002.1c09e027@kernel.org>

On Tue, 5 Dec 2023 at 10:10, Jakub Kicinski <kuba@kernel.org> wrote:
>
> Hopefully the merge window for v6.8 will open on Jan 7th or 14th,
> giving us at least a week to settle any -next code which is ready
> after the break.

Just FYI - my current plan is that -rc7 will happen this Saturday
(because I still follow the Finnish customs of Christmas _Eve_ being
the important day, so Sunday I'll be off), and then if anything comes
in that week - which it will do, even if networking might be offline -
I'll do an rc8 the week after.

Then, unless anything odd happens, the final 6.7 release will be Jan
7th, and so the merge window for 6.8 will open Jan 8th.

So that's the plan, and it doesn't look like there's anything strange
going on that would cause me to delay any further, so it's pretty
likely to hold. Knock wood.

                   Linus

      parent reply	other threads:[~2023-12-21 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 18:10 [ANN] Winter break shutdown plan Jakub Kicinski
2023-12-06  2:01 ` Alexei Starovoitov
2023-12-21 15:00 ` Paolo Abeni
2023-12-21 18:09 ` Linus Torvalds [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='CAHk-=whceLbGZwuLnR0S3V_ajedDXj=s86sm89m+VT2YrbG1NA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=bpf@vger.kernel.org \
    --cc=fw@strlen.de \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=kvalo@kernel.org \
    --cc=netdev-driver-reviewers@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.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.