All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: fast-forwarding tags
Date: Wed, 25 Sep 2013 12:28:20 -0700	[thread overview]
Message-ID: <20130925192820.GZ9464@google.com> (raw)
In-Reply-To: <20130925113651.GA19023@redhat.com>

Hi,

Michael S. Tsirkin wrote:

> Linus favors one-time use signed tags, e.g. for_linus.
> Unfortunately if I push to such a tag without -f,
> I get an error ("already exists").
> Would it make sense for there to be an option that makes it behave like
> a head, and allow fast-forward?

Nah, I think I prefer keeping the safety. :)

Are you pushing with "git push --tags", "git push --follow-tags", "git
push origin tag for-linus", or "git push origin for-linus"?  It's
possible that the last two should *always* allow overwriting tags
(regardless of whether the change is a fast-forward update), though I
haven't thought it through carefully.  In the former two cases, the
check for moving an existing tag seems useful and worth preserving.

In the meantime, a command like "git push origin +for-linus" seems
like a pleasant way to get the job done.  That way, nothing bad
happens if you get distracted and forget to add the for-linus argument
(unlike "git push -f origin").

Thanks,
Jonathan

      reply	other threads:[~2013-09-25 19:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25 11:36 fast-forwarding tags Michael S. Tsirkin
2013-09-25 19:28 ` Jonathan Nieder [this message]

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=20130925192820.GZ9464@google.com \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mst@redhat.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.