git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Jabber, question on push,pull and --tags, and no help but jabber

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Jun 6, 2011, 14:31 UTC
Message-ID
<4DECE4D6.9000204@drmicha.warpmail.net>
In-Reply-To
<20110606130205.GA41674@sherwood.local>
Steffen Daode Nurpmeso venit, vidit, dixit 06.06.2011 15:02:
Show 19 quoted lines
> 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.

Show 16 quoted lines
> 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

Previous: Steffen Daode NurpmesoNext: Felipe Contreras
Message 2 of 14 in “Jabber, question on push,pull and --tags, and no help but jabber”
  1. Steffen Daode NurpmesoJun 6, 2011
  2. Michael J GruberJun 6, 2011
  3. Felipe ContrerasJun 6, 2011
  4. Steffen Daode NurpmesoJun 6, 2011
  5. Michael J GruberJun 7, 2011
  6. Steffen Daode NurpmesoJun 7, 2011
  7. Notes that tags need to pushed explicitelySteffen Daode Nurpmeso, Jun 7, 2011
  8. Junio C HamanoJun 7, 2011
  9. Remarks that tags need to be pushed explicitlySteffen Daode Nurpmeso, Jun 7, 2011
  10. Remarks that tags need to be pushed explicitlySteffen Daode Nurpmeso, Jun 10, 2011
  11. Junio C HamanoJun 10, 2011
  12. Steffen Daode NurpmesoJun 11, 2011
  13. Victor EngmarkJun 6, 2011
  14. Junio C HamanoJun 6, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.