Comment 4 for bug 252894

Revision history for this message
James Westby (james-w) wrote : Re: [Bug 252894] Re: generally applicable way to refer to parent or stored locations

On Tue, 2008-07-29 at 11:13 +0000, RLVJ wrote:
> I was meaning a way to refer to the parent of the current branch for any
> operation.

That's what the ":parent" notation allows.

>
> This could be ambiguous in the case of nested branches.
> For a nested branch, does the operation (push) refer to the parent of the encompassing branch or the nested branch?
>

It will refer to the parent of the nested branch.

Could we close this bug as being fixed in the 1.6 release with the
":parent" notation? It seems like it implements what you want.

> Some more flexible and difficult to implement functionality would be to allow for arbitrary levels of indirection, including things like:
> parent of the parent of the encompassing branch of the current branch.
>

I'm not sure why you'd ever want to do this, could you explain please?

For the encompassing branch part the two branches are not likely
to be compatible in the nested tree case, so
"bzr push :parent-of-encompassing-branch" will fail.

As for arbitrary nesting of this, i.e. "bzr push :parent:parent", it
would be possible, but once you get beyond 2 levels it's probably
hard to remember which branch you are referring to, and so using URLs
is proabably going to be easier. You don't need to think "was it
:parent:submit:parent, or :parent:parent:submit".

Thanks,

James