git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC 1/6] tag: read signature
Date: Sun, 22 Feb 2009 10:18:24 -0800	[thread overview]
Message-ID: <7vskm6xrm7.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <e29894ca0902221006y4b0e29e7ucc8a04e8e6e42f4@mail.gmail.com> (Marc-André Lureau's message of "Sun, 22 Feb 2009 20:06:37 +0200")

Marc-André Lureau <marcandre.lureau@gmail.com> writes:

> diff --git a/tag.h b/tag.h
> index 7a0cb00..bc2cab3 100644
> --- a/tag.h
> +++ b/tag.h
> @@ -9,7 +9,7 @@ struct tag {
>  	struct object object;
>  	struct object *tagged;
>  	char *tag;
> -	char *signature; /* not actually implemented */
> +	char *signature;
>  };

I do not speak for Daniel, but I think the original intent of "signature"
is about the GnuPG signature, not the "tagger" field.

And this is not an objection.  The use of GnuPG is accidental and at the
low level of the object layer like this codepath we would not necessarily
want to be married to it.  Grabbing and parsing the tagger field like your
patches 1/6 and 2/6 did would be more appropriate.

But then we would probably want to rename this field "tagger" (and then
the timestamp field you add in the next patch "tagger_date").

  reply	other threads:[~2009-02-22 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 18:06 [PATCH/RFC 1/6] tag: read signature Marc-André Lureau
2009-02-22 18:18 ` Junio C Hamano [this message]
2009-02-22 18:25   ` Marc-André Lureau

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=7vskm6xrm7.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=marcandre.lureau@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).