From: "Carlos Rica" <jasampler@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Pierre Habouzit" <madcoder@debian.org>, git@vger.kernel.org
Subject: Re: Wishlist: Please add --author to git-tag
Date: Fri, 1 Feb 2008 15:48:42 +0100 [thread overview]
Message-ID: <1b46aba20802010648j6f305cbve55d50d1ead74a73@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0801312345520.23907@racer.site>
On Feb 1, 2008 12:48 AM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
> On Thu, 31 Jan 2008, Carlos Rica wrote:
>
> > On Jan 31, 2008 8:35 PM, Pierre Habouzit <madcoder@debian.org> wrote:
> > > On Thu, Jan 31, 2008 at 05:27:31PM +0000, 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.
> > >
> > > Meanwhile,
> > >
> > > GIT_AUTHOR_NAME="John Doe" GIT_AUTHOR_EMAIL=luser@example.com git tag
> >
> > That didn't work for me,
>
> Hey jasam, good to see you again.
>
> I think that you have to use "-s" or "-a" for the author information to
> take effect (IOW a lightweight tag will not pick it up, since it is only a
> 41-byte file, and does not change the object database).
This way it doesn't work for me either. You know, the tag object has
only a "tagger", who is always the committer. Currently, I'm inspecting
the resulting object using "git cat-file tag t". I cannot find where that author
name specified in the command line should be stored for tags.
It is nice to see you too!
Carlos
next prev parent reply other threads:[~2008-02-01 14:49 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 [this message]
2008-02-16 19:49 ` Rhodes, Kate
2008-02-18 0:00 ` Nicolas Pitre
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=1b46aba20802010648j6f305cbve55d50d1ead74a73@mail.gmail.com \
--to=jasampler@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=madcoder@debian.org \
/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).