Re: keeping track of where a patch begins

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Pascal Obry wrote:
> 
> 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
[...]
> 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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]