From: Paolo Bonzini <bonzini@gnu.org>
Date: Wed, 10 Sep 2008 15:24:35 GMT
Subject: Re: [RFC] origin link for cherry-pick and revert, and more about porcelain-level metadata
Message-ID: <48C7E6B3.7030403@gnu.org>
In-Reply-To: <20080910151542.GA10523@cuci.nl>

> > > fork topic branches off the older branch [and merge them]
>
> Could you explain how the above mechanisms work based on the following
> cherry-pick action:
> 
> A -- B -- C -- D -- L
>       \            /
>        E -- F -- G -- H -- K
> 
> D is the stable branch.
> K is the development branch.
> G is cherry-picked and applied to D producing L.
> The origin link of L would have contained (G, F).
> 
> How would such a workflow be implemented using the temporary branches
> you describe?

You don't.  You do everything in topic branches based off the stable
branch, and you merge them.  That's the other way round, compared to
what you (and I) are used to.

Paolo