-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- From `cg-push --long-help`:
- -t TAG::
Tells cg-push to also push the given tag. Note that in the
future, cg-push should push tags automatically. Also note
that even if you pass `cg-push` the '-t' arguments, your
HEAD is still pushed as well in addition to the tags.
One of possible ways of doing it is in attached patch. Comments,
suggestions?
- --
Krzysiek Pawlik (Nelchael)
RLU #322999 GPG Key ID: 0xBC555551
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFEK9Vigo/w9rxVVVERAvXkAJ42ESjs3REY0ECqIYlbz+9WX/3+ZQCfSQs/
B4X6U2io0Wq0/0oiolpUW1g=
=3ZR7
-----END PGP SIGNATURE-----
Dear diary, on Thu, Mar 30, 2006 at 02:56:02PM CEST, I got a letter
where Krzysiek Pawlik [off-list ref] said that...
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- From `cg-push --long-help`:
- -t TAG::
Tells cg-push to also push the given tag. Note that in the
future, cg-push should push tags automatically. Also note
that even if you pass `cg-push` the '-t' arguments, your
HEAD is still pushed as well in addition to the tags.
One of possible ways of doing it is in attached patch. Comments,
suggestions?
Well, this works properly only when you ever push to a single
repository, which many people don't. Besides, if you have two branches,
push branch A but tag a commit only on branch B, you will now be pushing
an invalid tag since the other end won't have the branch B and thus the
tagged commit.
A better way would be to use git-ls-remote --tags to get the list of
remote tags and compare that with the list of local tags, then push
those tags that tag commits on the branch we are pushing and the other
end does not have them.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
A person is just about as big as the things that make them angry.