From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mark Brown <broonie@kernel•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: a couple of breaks
Date: Thu, 6 Apr 2023 09:53:12 +1000 [thread overview]
Message-ID: <20230406095312.2a75ad36@canb.auug.org.au> (raw)
In-Reply-To: <31ea09c7-7187-4d44-a25a-cd5378cefd69@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
Hi Mark,
On Wed, 5 Apr 2023 12:06:55 +0100 Mark Brown <broonie@kernel•org> wrote:
>
> On Wed, Apr 05, 2023 at 04:57:07PM +1000, Stephen Rothwell wrote:
>
> > There will be no linux-next releases over the coming Easter long
> > weekend i.e. no release on Friday or Monday.
>
> > After that, I will be on vacation from April 13 to May 7 inclusive. So
> > Wednesday April 12 will be the last release I do until May 8.
> > Unfortunately, that means I will miss the whole next merge window.
>
> I'll try to provide coverage for for the part of this that's in April,
> I won't be able to cover the first week of May unfortunately.
That should be the second week of the merge window, so not a big issue.
>
> I'll not cover the coming weekend.
Sounds good - whatever you can reasonably do, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-04-05 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 6:57 linux-next: a couple of breaks Stephen Rothwell
2023-04-05 11:06 ` Mark Brown
2023-04-05 23:53 ` Stephen Rothwell [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=20230406095312.2a75ad36@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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