Common ancestor in a repository?
Brian de Alwis
briandealwis at gmail.com
Fri Mar 29 14:07:16 UTC 2013
You can do:
$ bzr log -c ancestor:.../path/to/branch
On 29-Mar-2013, at 1:53 AM, John Meinel wrote:
> There is "bzr qlog a b c" from the qbzr plugin. I think some of its logic for how to lay out multiple branch ancestries is in core bzr. At least, there was effort to make it common so it could be used in web front ends like loggerhead. But I don't think all of that was completed.
> If you just want common ancestors of >2 branches, I'm pretty sure the internal Graph object handles it. But it isn't something that got exposed to the command line.
> On Mar 28, 2013 8:49 PM, <ckalisiak at attotech.com> wrote:
> Thanks to the assistance of John Arbash Meinel, we have been able to
> identify how we should
> be dealing with point fixes and code sharing between branches.
> The next step is how to determine programmatically the greatest common
> ancestor of a number
> of branches in a respository.
> I'm aware of "find-merge-base", which is a good start, but it only
> operates on two branches at a
> time, and its output is only useful as the input to another command (e.g.
> bzr log). I'm also aware of
> "ancestry" and "graph-ancestry", which provides more detail of the history
> of a particular branch.
> Does there exist a mechanism for graphing the merge history of all
> branches contained in a
> Chris Kalisiak
> Senior Embedded Systems Engineer
> ATTO Technology, Inc.
> Phone: +1.716.691.1999 ext. 274
> Fax +1.716.691.9353
> "Powering the World's Networks & Storage"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bazaar