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. > heavily scripted page of my free private repo webhoster :-) and > don't see any tags, even though i've pushed multiple times and > v0.0.0 was created directly after the first commit. I would *not* > have detected that otherwise ... > (Yes i know it's somewhat implied by 'git help push'..--tags. > But i'm blonde.) > > Some more i'll pack into this so that it's gone with the wind: > > - Due to my weak GPRS or noisy HDSPA radio connection here in the > pampa :) i hope for continuable network actions - failing after > 98% is a costly pain. So it was a real joy to read somewhere > that a GSOC project will address this issue!! > - OpenSSL support for signing. I don't use PGP/GPG. But i use > HTTPS, POPS, SSH etc., so i'll have an OpenSSL/OpenSSH > environment here on my box ready to use. "git tag" and "git verify-tag" call out to "gpg". That could be easily adapted to call out to "openssl smime", or put your S/MIME signatures in a note. Cheers Michael -- 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