git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: "Rhodes, Kate" <masukomi@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Wishlist: Please add --author to git-tag
Date: Sun, 17 Feb 2008 19:00:07 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.1.00.0802171859010.2732@xanadu.home> (raw)
In-Reply-To: <420D37FF-C808-47CA-A3C8-38E1F8578FAC@gmail.com>

On Sat, 16 Feb 2008, Rhodes, Kate wrote:

> 
> On Jan 31, 2008, at 12:27 PM, Daniel Baumann wrote:
> 
> > git commit supports --author to overwrite the author information on a
> > particular commit; it would be nice if git tag would offer the same.
> 
> What are the implications of this on the GPG signature aspect of git-tag
> (desired or otherwise)?
> 
> If you were committing someone else's tag wouldn't you want to sign not only
> the commit, but their signature on the commit?
> 
> Ignoring the GPG issue, I'm just not seeing the benefit to having an author
> AND a committer on a tag. I mean... it's a *tag*. The only value I see in
> having any name associated with a tag is knowing who to point the finger at
> when the wrong thing gets tagged. But, I don't see any authorship aspect to
> the concept of a tag. To me it's more: "Bob" set it and it points to this. The
> end.
> 
> What you're proposing sounds more like: "Bob" said to set it and then "Mary"
> did, because Bob said to.

And in that case this information can be contained in the tag text body 
itself.


Nicolas

      reply	other threads:[~2008-02-18  0:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 17:27 Wishlist: Please add --author to git-tag Daniel Baumann
2008-01-31 19:35 ` Pierre Habouzit
2008-01-31 22:49   ` Carlos Rica
2008-01-31 23:48     ` Johannes Schindelin
2008-02-01 14:48       ` Carlos Rica
2008-02-16 19:49 ` Rhodes, Kate
2008-02-18  0:00   ` Nicolas Pitre [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=alpine.LFD.1.00.0802171859010.2732@xanadu.home \
    --to=nico@cam.org \
    --cc=git@vger.kernel.org \
    --cc=masukomi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).