Re: Jabber, question on push,pull and --tags, and no help but jabber
- From
Felipe Contreras <felipe.contreras@gmail.com>
- Date
- Jun 6, 2011, 15:21 UTC
- Message-ID
- <BANLkTikYhWxONOCaPx7P0RX6By6GmEum=g@mail.gmail.com>
- In-Reply-To
- <4DECE4D6.9000204@drmicha.warpmail.net>
On Mon, Jun 6, 2011 at 5:31 PM, Michael J Gruber <git@drmicha.warpmail.net> wrote:
Show 28 quoted lines
> 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