[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110513213640.GB30539@n2100.arm.linux.org.uk>
Date: Fri, 13 May 2011 22:36:40 +0100
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Ingo Molnar <mingo@...e.hu>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
John Stultz <john.stultz@...aro.org>,
Jacob Pan <jacob.jun.pan@...el.com>,
Glauber Costa <glommer@...hat.com>,
Dimitri Sivanich <sivanich@....com>,
Rusty Russell <rusty@...tcorp.com.au>,
Jeremy Fitzhardinge <jeremy@...source.com>,
Chris McDermott <lcm@...ibm.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Subject: Re: linux-next: manual merge of the tip tree with the arm tree
On Fri, May 13, 2011 at 11:26:46AM +0200, Ingo Molnar wrote:
> Had you asked us before committing it one day after it was posted, or had you
> *noticed* that those files are not in your tree and are already modified in
> linux-next, you'd have gotten a response like:
Please also don't read anything into the commit date - it merely shows
when the last update happened.
My workflow for patch series involves keeping them in git right from the
start. So actually they've been in git since _before_ they were posted.
In fact, the emails which I send out for any patch series are always
generated from the git commits.
So, all my patches live in git _first_ before being mailed out.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists