overview of stacked branch

William Dode wilk at flibuste.net
Wed Jul 9 08:36:59 BST 2008

On 09-07-2008, Ian Clatworthy wrote:
> William Dode wrote:
>> On 03-07-2008, Ian Clatworthy wrote:
>>> More interesting is pushing a new branch that only contains the
>>> changes from a nominated other branch. In most cases, the branch
>>> to stack on will be implicit. The end result will be something like:
>>>   bzr branch trunk-url
>>>   hack, hack, hack
>>>   bzr push --stacked my-bug-fix-url
>>> I hope that gives you a rough idea of how things will look at the
>>> UI level. Pretty cool, eh!
>> Then, what will append under ?
> Assuming I'm understanding your question, the new branch will
> store just the new revisions together with a reference back to the
> other branch. When you access the new branch, it will transparently
> get revisions from the right place.

It was my question :-)

And then when it get revisions from the remote place, does it keep it 
for the next time ?


William Dodé  -  http://flibuste.net
Informaticien indépendant

More information about the bazaar mailing list