[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8yaei7n1xw4.fsf@huya.qualcomm.com>
Date: Fri, 04 Feb 2011 10:02:19 -0800
From: David Brown <davidb@...eaurora.org>
To: Russell King <rmk@....linux.org.uk>
Cc: Daniel Walker <dwalker@...eaurora.org>,
Nicolas Pitre <nico@...xnic.net>, Greg KH <greg@...ah.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, lkml <linux-kernel@...r.kernel.org>,
Stepan Moskovchenko <stepanm@...eaurora.org>,
linux-arm-msm@...r.kernel.org
Subject: Re: linux-next: manual merge of the msm tree with the arm tree
On Fri, Feb 04 2011, Russell King wrote:
> I really don't care which - but I'll warn you that keeping changes
> hidden will result in a reduction of patch quality, and much much
> much less testing of those changes. And I won't care at all when you
> complain that MSM's broken because of one of my patches.
>
> Exactly what would you prefer?
I'd like to get a little bit of an idea what you would prefer me to do.
I see two reasonable workflows:
- I make a branch for the files that conflict with other changes in
the ARM tree and submit pull requests to you (Russell) for these
changes. Other MSM-specific changes would be in another tree that
goes to Linus.
- I submit everything via pull requests to you. This would probably
result in one additional request to you, that contained the stuff
that didn't conflict, since it would be nice to resolve the obvious
conflicts earlier.
The later is more work for you, and less for Linus.
Thanks,
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
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