git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH/RFC 1/6] tag: read signature

From
Marc-André Lureau <marcandre.lureau@gmail.com>
Date
Feb 22, 2009, 18:25 UTC
Message-ID
<e29894ca0902221025t5e015c96ycb90afaec4a33124@mail.gmail.com>
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:
Show 25 quoted lines
> 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.
Previous: Junio C Hamano
Message 3 of 3 in “tag: read signature”
  1. 1/6 tag: read signatureMarc-André Lureau, Feb 22, 2009
  2. Junio C HamanoFeb 22, 2009
  3. Marc-André LureauFeb 22, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.