From: Mark Brown <broonie@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Oct 25
Date: Sat, 26 Oct 2013 17:59:37 +0100 [thread overview]
Message-ID: <20131026165937.GA6362@sirena.org.uk> (raw)
In-Reply-To: <526AF150.1030004@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
On Fri, Oct 25, 2013 at 03:31:44PM -0700, Randy Dunlap wrote:
> That's unfortunate. The fixes should be part of the tree IMO.
What Stephen does (which does seem like a good policy) is to keep the
tree at the previous day's version instead of taking a new version if it
introduces breakages on the architectures he tests. That seems to
strike a good balance between keeping things working for users and
providing pushback to get things fixed before they go to Linus.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-10-26 17:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 15:03 linux-next: Tree for Oct 25 Thierry Reding
2013-10-25 15:03 ` linux-next: manual merge of the block tree Thierry Reding
2013-10-25 19:46 ` linux-next: Tree for Oct 25 (powercap_sys.c) Randy Dunlap
2013-10-25 22:17 ` Srinivas Pandruvada
2013-10-25 22:30 ` Srinivas Pandruvada
2013-10-25 21:01 ` linux-next: Tree for Oct 25 Guenter Roeck
2013-10-25 21:12 ` linux-next: Tree for Oct 25 (of_gpio.h) Randy Dunlap
2013-10-25 22:31 ` linux-next: Tree for Oct 25 Randy Dunlap
2013-10-26 16:59 ` Mark Brown [this message]
2013-10-28 8:01 ` Thierry Reding
2013-10-28 16:53 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2022-10-25 4:20 Stephen Rothwell
2021-10-25 9:49 Stephen Rothwell
2021-10-25 22:11 ` Dmitry Osipenko
2021-10-26 1:28 ` Ming Lei
2021-10-26 8:40 ` Dmitry Osipenko
2021-10-27 11:42 ` Stephen Rothwell
2021-10-27 12:54 ` Greg Kroah-Hartman
2021-10-28 1:51 ` Xianting Tian
2021-10-28 4:51 ` Stephen Rothwell
2021-10-28 7:59 ` Xianting Tian
2021-10-28 12:48 ` Stephen Rothwell
2021-10-28 12:54 ` Xianting Tian
2019-10-25 5:45 Stephen Rothwell
2016-10-25 3:31 Stephen Rothwell
2016-10-26 1:09 ` Paul Gortmaker
2016-10-27 6:21 ` Daniel Vetter
2012-10-25 4:01 Stephen Rothwell
2011-10-25 9:36 Stephen Rothwell
2011-10-25 9:43 ` Stephen Rothwell
2011-10-25 10:42 ` Stephen Rothwell
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=20131026165937.GA6362@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).