From: Joe Perches <joe@perches•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Fengguang Wu <fengguang.wu@intel•com>
Subject: Re: linux-next: Tree for Sep 25
Date: Wed, 25 Sep 2013 17:47:28 -0700 [thread overview]
Message-ID: <1380156448.17366.44.camel@joe-AO722> (raw)
In-Reply-To: <20130925144329.7d240a6fa2b5782dc8726340@canb.auug.org.au>
On Wed, 2013-09-25 at 14:43 +1000, Stephen Rothwell wrote:
> Hi all,
>
> Heads up: I will be having a 3 week break leading up to the kernel
> summit. This means that next-20130927 (next Friday) will be the last
> linux-next release until next-20131028 (or maybe 29). I presume that
> Linus will be up to v3.12-rc7 by then and -rc7 is often the last before
> a release ... Please plan accordingly.
Hi Stephen.
Maybe this is a good time for an experiment.
Perhaps it would be interesting if you still had a script
running every workday and pushed out the result tree without
trying to do any patch conflict resolution yourself.
Maybe notify the owners of the trees that conflict and let
them work out whatever resolutions that are necessary.
I think FengGuang's robot can supply most all the details
necessary and maybe you can do a lot less work in the future.
next prev parent reply other threads:[~2013-09-26 0:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 4:43 linux-next: Tree for Sep 25 Stephen Rothwell
2013-09-26 0:47 ` Joe Perches [this message]
2013-10-03 13:30 ` Fengguang Wu
2013-10-03 16:47 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2014-09-25 8:34 Stephen Rothwell
2015-09-25 5:04 Stephen Rothwell
2018-09-25 5:39 Stephen Rothwell
2019-09-26 2:21 Mark Brown
2020-09-25 10:55 Stephen Rothwell
2023-09-25 4:52 Stephen Rothwell
2024-09-25 3:05 Stephen Rothwell
2025-09-25 16:22 Mark Brown
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=1380156448.17366.44.camel@joe-AO722 \
--to=joe@perches$(echo .)com \
--cc=fengguang.wu@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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