How to handle 'tag pushing revisions' and stacking

[vila]

>>>>> John Arbash Meinel <john at arbash-meinel.com> writes:

<snip/>

    > I would imagine that co-located branches might scale to ~50 branches or
    > so at best. (Beyond that, you have >1 screens full of branch names to
    > sift through to find the 'current' stuff.)

Good point but easily addressed by providing filtering and supporting
some hierarchical name spaces there.

    >> 
    >> I think Vincent has a point that we could consider only looking at those
    >> tags that we are changing. We could add an option to have bzr push look
    >> really hard for missing revisions; this would also take care of another
    >> open bug about filling in ghosts during push if an option is specified.
    >> 
    >> Cheers,
    >> 
    >> Jelmer

    > ATM we don't know what tags we are changing at the appropriate levels.
    > It happens at very different locations. Consider that a stacked branch
    > doesn't *have* any tags yet. So we are changing all of them. (you could
    > arguably recurse to the stacked-on branch and only do the delta there,
    > but it isn't a trivial "what do I have that the target doesn't have".)

Doesn't the union of tags (across the stack) on both sides answer that ?
The upload target is unambiguous anyway.

        Vincent