From: "Marc-André Lureau" <marcandre.lureau@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC 1/6] tag: read signature
Date: Sun, 22 Feb 2009 20:25:21 +0200 [thread overview]
Message-ID: <e29894ca0902221025t5e015c96ycb90afaec4a33124@mail.gmail.com> (raw)
In-Reply-To: <7vskm6xrm7.fsf@gitster.siamese.dyndns.org>
Hi
On Sun, Feb 22, 2009 at 8:18 PM, Junio C Hamano <gitster@pobox.com> wrote:
> 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").
>
Yes, I though the same. But when I saw the way it was parsed before
(the value of sig_line), I was not sure about naming.
I agree it would be better to name it "tagger".
regards,
--
Marc-André Lureau
Sent from: Helsinki Southern Finland Finland.
prev parent reply other threads:[~2009-02-22 18:26 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
2009-02-22 18:25 ` Marc-André Lureau [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=e29894ca0902221025t5e015c96ycb90afaec4a33124@mail.gmail.com \
--to=marcandre.lureau@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 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).