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

[Steffen Daode Nurpmeso <sdaoden@googlemail.com>]

@ Michael J Gruber <git@drmicha.warpmail.net> wrote (2011-06-06 16:31+0200):
> "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

Hum.  It will indeed be possible to place a wrapper script 'gpg'
in the path on my box (and catch '--verify' - or sign otherwise).

But in the meanwhile i've found out that git(1) is heavily
developed, stale .git_vtag_ files of an 1.7.3? version are no
longer produced by 'git version 1.7.6.rc0' to which i've updated
after i've seen those.  So maybe there is hope that the hardcoded
gpg invocation will be replaced by configuration options in the
future, too?

I still don't understand the design with pull and --tags.
Because, if i do 'git log' it'll display the relationship as in

    commit fd040fb[...] (tag: refs/tags/v0.3.0, refs/remotes/origin/master)

So i'll push this commit object as part of pushing a branch, and
the tag refers to *it*.  I don't want to be impertinent though,
and it's better that explicit way than implicitely pushing some
distressing stuff.  Still i would have appreciated a note in the
docu, because it took a look at the mentioned webspace to realize
the situation.  I'll append a short diff to be able to provide
something useful.  (No attachments allowed here i guess.)

I'll try to be less tiny from the start the next time.
--
Ciao, Steffen
sdaoden(*)(gmail.com)
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments

--
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index 88acfcd..da4a71a 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -69,7 +69,7 @@ nor in any Push line of the corresponding remotes file---see below).
 
 --all::
 	Instead of naming each ref to push, specifies that all
-	refs under `refs/heads/` be pushed.
+	refs under `refs/heads/` be pushed explicitely.
 
 --mirror::
 	Instead of naming each ref to push, specifies that all
@@ -98,7 +98,7 @@ nor in any Push line of the corresponding remotes file---see below).
 --tags::
 	All refs under `refs/tags` are pushed, in
 	addition to refspecs explicitly listed on the command
-	line.
+	line.  Note that tags are not pushed automatically.
 
 --receive-pack=<git-receive-pack>::
 --exec=<git-receive-pack>::