Re: keeping track of where a patch begins

From: Thomas Rast <trast@student.ethz.ch>
Date: Oct 30, 2009, 08:37 UTC
Message-ID: <200910300937.22949.trast@student.ethz.ch>
In-Reply-To: <4AEA94EB.8080304@obry.net>

Pascal Obry wrote:

Show 5 quoted lines

> 
> Le 22/10/2009 10:27, Thomas Rast a écrit :
> > I think this not only changes the model of branches, but also commits,
> > to some extent.  Currently, commit have no intrinsic branch
> > membership

[...]

Show 9 quoted lines

> To me there is case where it is important to know which are the commits 
> done on a topic branch for example. When working on multiple topic it is 
> difficult to remember which commits have been done on this specific 
> branch. This is needed to rebase onto:
> 
>     $ git rebase --onto somebranch <topic_base> <topic_head>
> 
> A common idiom, but one as to think hard (& right) to properly get the 
> topic_base today.

But how frequently do your topics start on other topics? Otherwise they will start on an integration or maint branch, and in the git.git model where each integration branch is contained in the next "less stable" one, that means you can just specify 'pu' or equivalent.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch