On Mon, Jun 6, 2011 at 5:31 PM, Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> wrote: > Steffen Daode Nurpmeso venit, vidit, dixit 06.06.2011 15:02: >> Hello GIT, >> Â Â first paragraph is reserved for praising your existence. >> Â Â 'Used cvs(1) for long years in small team projects with local >> Â Â private repos and never felt the need for anything else. Â2011 >> Â Â is different. ÂI first tried you but failed resoundingly. ÂDue >> Â Â to vim(1) and mutt(1) i discovered hg(1) and i still love it's >> Â Â simple usage. Â'Talking about the front-end anyway. ÂIt's huge >> Â Â memory consumption and slow performance forbids it's usage on >> Â Â our old PCs (e.g. Cyrix 166+) though. ÂSo i came back and >> Â Â found you still receptive! ÂAnd the more i work, the less >> Â Â i hurt, the greater the knowledge, the smoother the >> Â Â interaction. ÂAre you the final word on RC in the end? >> >> I stumbled over one thing i don't understand, because it seems >> illogical: why do i need to use --tags to force pushing of tags? >> Because there is even a config option for the latter, i suspect >> this is because of intention. ÂIt would be nice to get some >> information on the background of that, like a link to yet existing >> documentation. ÂAnyway i was a bit astonished to look at some > > Tags may contain private information. Say you pull some changes from > your head of group, find a strange commit you want to look at later and > tag it with "what-is-this-crap"... > > More seriously, tags are not part of the "remotes layout", so when you > push them and others pull them they overwrite their tags if there's a > name clash. Until tag namespaces are merged. -- Felipe Contreras -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html