From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Darling <darlingm@gmail.com>, git@vger.kernel.org
Subject: Re: BUG: For first push to a bare repo, using "--tags" prevents creation of master branch
Date: Fri, 29 May 2015 17:45:06 +0200 [thread overview]
Message-ID: <vpq4mmvs7zx.fsf@anie.imag.fr> (raw)
In-Reply-To: <xmqq617bflzh.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Fri, 29 May 2015 08:21:22 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Yeah. I am not sure --tags-also is necessarily a good thing (I do
> not think "fetch --tags" is a good thing, either). If --follow-tags
> does not touch lightweight ones, that may be a bug we would want to
> fix. I did not mean to implement --follow-tags that way, and I do
> not offhand remember if there was a reason to omit lightweight ones.
It's documented to push only annotated tags both in the commit message
of c2aba15 (push: --follow-tags, 2013-03-04) and in the man page, so it
was done on purpose, but I don't know if it was a good thing.
Perhaps a justification is that annotated tags are clearly meant to be
public while lightweight tags can also be used as private bookmarks.
In any case, the fact that it's been this way and documented this way
since 2013 makes it a bit hard to change now.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2015-05-29 15:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 0:10 BUG: For first push to a bare repo, using "--tags" prevents creation of master branch Michael Darling
2015-05-29 5:35 ` Matthieu Moy
2015-05-29 15:21 ` Junio C Hamano
2015-05-29 15:45 ` Matthieu Moy [this message]
2015-05-29 16:05 ` Junio C Hamano
2015-05-29 16:40 ` Junio C Hamano
2015-05-29 17:53 ` Matthieu Moy
2015-05-29 18:03 ` Junio C Hamano
2015-06-02 23:48 ` Not a " Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpq4mmvs7zx.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=darlingm@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.