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

Re: [PATCH] builtin-tag.c: remove global variable to use the callback data of git-config.

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 17, 2009, 18:45 UTC
Message-ID
<7vljr4q97u.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1b46aba20903171057r4fb4697eo3b8abc62a45fe858@mail.gmail.com>
Carlos Rica <jasampler@gmail.com> writes:
Show 25 quoted lines
> On Tue, Mar 17, 2009 at 4:47 PM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>> Hi,
>> On Tue, 17 Mar 2009, Carlos Rica wrote:
>>> @@ -164,11 +162,10 @@ static int do_sign(struct strbuf *buffer)
>>>       int len;
>>>       int i, j;
>>>
>>> -     if (!*signingkey) {
>>> -             if (strlcpy(signingkey, git_committer_info(IDENT_ERROR_ON_NO_NAME),
>>> -                             sizeof(signingkey)) > sizeof(signingkey) - 1)
>>> -                     return error("committer info too long.");
>>> -             bracket = strchr(signingkey, '>');
>>> +     if (!signingkey->buf[0]) {
>>
>> It is probably better to ask for !signingkey->len (think of trying to
>> understand the code in 6 months from now).
>
> I was in doubt here. By avoiding the use of signingkey->len  I was
> trying to say that you cannot rely in such field if we touch the
> buffer directly, as it happens below:
>
>    bracket = strchr(signingkey->buf, '>');
>    if (bracket)
>       bracket[1] = '\0';
That's a wrong use of strbuf, isn't it?
Previous: Carlos RicaNext: Johannes Schindelin
Message 4 of 6 in “builtin-tag.c: remove global variable to use the callback data of git-config.”
  1. builtin-tag.c: remove global variable to use the callback data of git-config.Carlos Rica, Mar 17, 2009
  2. Johannes SchindelinMar 17, 2009
  3. Carlos RicaMar 17, 2009
  4. Junio C HamanoMar 17, 2009
  5. Johannes SchindelinMar 17, 2009
  6. Carlos RicaMar 18, 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.