Re: [rfd] auto-following tags upon "git push"?

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

If there would be a free bit somewhere in a tag object (or so):

    $ git tag --autopush -ma "This will be pushed along it's commit" T1

This i would understand at a glance!
And it is both, explicit on the one and automatic on the other
hand.  I.e.: work, work, work - commit & tag, hours pass until
internet access and then

    $ if-up-and-push-it-all-and-if-down.sh

.. and that would only do 'cd repo && git push'.
But having a short look into tag.c does not give much hope on that.
Maybe a new file .git/AUTOPUSH to which all SHA-1 to be
pushed automatically are simply appended.

@ Junio C Hamano <gitster@pobox.com> wrote:
>    Tell git that v*.* and v*.*.* are release tags (one-time set-up).
>    $ git config --unset-all push.autotag
>    $ git config --add push.autotag 'v*.*'
>    $ git config --add push.autotag 'v*.*.*'

I will blow that one, one of these days.

@ Jeff King <peff@peff.net> wrote:
> Hmm. Is it a clear enough hint when the user uses an actual tag
> object to make a signed or annotated tag? At least for me,
> private throw-away tags tend to just be refs/tags/foo pointing
> to a commit, and real, for-public-consumption tags at least get
> an annotation, if not a signature.
> [.] Anyway, the problem would be somebody who does something like:
>
>  $ git tag -m "here is a description of how this wip is going" foo-wip
>
> which violates the assumption above. I have no idea how common that is

I did understand that -m/-F required storage and thus force
creation of a tag object.  But hey - it's a bit odd, isn't it?
(Thinking about it some more it's very convenient that the
possibility exists.  But it will require more than one glance.
You know - that's ok for me, given all those features which will
make life easier once they're discovered and understood.)
--
Ciao, Steffen
sdaoden(*)(gmail.com)
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments