How to handle 'tag pushing revisions' and stacking

[John Arbash Meinel]

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


...
>     > 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


The point at which we upload tags is quite separated from the point at
which we fetch data (ATM). Further, it gets significantly more complex
if we say "all tags in stacked Branch that aren't in stacked-on Branch".

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk2YbgMACgkQJdeBCYSNAANpFgCgpSaj55SVOq/eQ2am2mGUot3h
GBQAn28zoHuytJNQbHOsrOzl+A8XZRAq
=yUTW
-----END PGP SIGNATURE-----