On 6 October 2011 02:36, Tim Bird <tim.bird@am.sony.com> wrote:

On 10/05/2011 08:37 AM, Andy Green wrote:

> Another side-issue is we are also looking at refactoring the
> Androidization patchset into topic branches, at the moment they're kind
> of reflecting the history that they were applied on plus or minus some
> munging around.  So, all the net core patches for example would be
> together in one series, then all the wireless ones in a series on top of
> that, etc.  It seems they would be easier to maintain then, opinions on
> that approach are also welcome.

I've been working on a set of broken-out Android patches, in quilt format,
with exactly the same goal.  It's much easier (at least for me) to maintain the
differences as distinct patches using quilt, rather than as a series (or set
of branches) of git commits.

But possibly I'm just missing how to do this easily with git.
I would very much like to compare approaches, and possibly share

Thanks a lot for the reply Tim.  I can describe how I manage this flow in detail.  Actually, since we would interact through pure git, it's not necessary to unify the patch management scheme to be able to cooperate.  But since I spent so much time on exactly this subject I guess we both find it interesting to describe it.