From: Mark Brown <broonie@kernel.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Joe Perches <joe@perches.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: linux-next: Tree for Sep 25
Date: Thu, 3 Oct 2013 17:47:08 +0100 [thread overview]
Message-ID: <20131003164708.GC27287@sirena.org.uk> (raw)
In-Reply-To: <20131003133051.GB25934@localhost>
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
On Thu, Oct 03, 2013 at 09:30:51PM +0800, Fengguang Wu wrote:
> It's a good idea, unfortunately Stephen has already went to vocation.
> I could try the auto merge and merge-failure reports and hand the
> script over to Stephen when he is back. However the merge conflicts
> will have to be handled by the relevant developer/maintainers.
Well, Thierry and myself are running this at the minute by hand so
perhaps there's not that much need. On the other hand doing the build
tests after each merge is rather resource intensive and that's where
your system excels - it'd be good to get the tree we're publishing
verified that way.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-03 16: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
2013-10-03 13:30 ` Fengguang Wu
2013-10-03 16:47 ` Mark Brown [this message]
-- 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=20131003164708.GC27287@sirena.org.uk \
--to=broonie@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=thierry.reding@gmail.com \
/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