Common ancestor in a repository?

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yes, we support finding the LCA for two branches at the commandline,
but we don't support finding the LCA for an arbitrary number of branches.

We could trivially extend find-merge-base to do this, I imagine.

Aaron

On 13-03-29 10:07 AM, Brian de Alwis wrote:
> You can do:
> 
> $ bzr log -c ancestor:.../path/to/branch
> 
> Brian.
> 
> 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. John =:->
>> 
>> On Mar 28, 2013 8:49 PM, <ckalisiak at attotech.com 
>> <mailto:ckalisiak at attotech.com>> wrote:
>> 
>> 
>> Hello,
>> 
>> 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 repository?
>> 
>> Thanks, Chris
>> 
>> -- 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"
>> 
>> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlFVub4ACgkQ0F+nu1YWqI3YkACaAh2/I2j/4oIoP86SFxfbUpXN
da8AmgN6HTcW4Ej5bzgwBdu6UN80AdNq
=oKV/
-----END PGP SIGNATURE-----