All of lore.kernel.org
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [Ksummit-2011-discuss] experience with the new arm-soc workflow (Was: Re: ARM Maintainers workshop at Kernel Summit) 2011
Date: Tue, 9 Aug 2011 16:34:18 +0100	[thread overview]
Message-ID: <20110809153418.GC3429@sirena.org.uk> (raw)
In-Reply-To: <1312902462.18583.254.camel@gandalf.stny.rr.com>

On Tue, Aug 09, 2011 at 11:07:42AM -0400, Steven Rostedt wrote:

> Where a clean up goes should be more about why the clean up is
> happening. If it is just a clean up for the sake of cleaning up, then a
> separate branch is suitable. But if a clean up is there to pave the way
> for new features, then that clean up should be with the features it
> allows to provide.

Though one of the frequent consequences of any widespread cleanup is
that it ends up touching lots of places and consequently colliding with
other work.

  reply	other threads:[~2011-08-09 15:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-06  6:44 ARM Maintainers workshop at Kernel Summit 2011 Grant Likely
2011-08-06 13:59 ` [Ksummit-2011-discuss] " Olof Johansson
2011-08-06 21:29   ` experience with the new arm-soc workflow (Was: Re: [Ksummit-2011-discuss] ARM Maintainers workshop at Kernel Summit) 2011 Uwe Kleine-König
2011-08-06 21:55     ` Nicolas Pitre
2011-08-06 22:13       ` Michał Mirosław
2011-08-07  4:11         ` David Brown
2011-08-09 15:07           ` [Ksummit-2011-discuss] experience with the new arm-soc workflow (Was: " Steven Rostedt
2011-08-09 15:34             ` Mark Brown [this message]
2011-08-09 15:41               ` Steven Rostedt
2011-08-09 15:57                 ` Mark Brown
2011-08-11 13:47     ` Arnd Bergmann
2011-08-09 14:15 ` ARM Maintainers workshop at Kernel Summit 2011 Sascha Hauer
2011-08-11  9:46   ` Marek Vasut
2011-08-11 13:32     ` Pavel Machek

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=20110809153418.GC3429@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.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.