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

Re: [PATCH] builtin-reflog.c: typo ref --> argv[i], could cause segfault

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 5, 2008, 01:22 UTC
Message-ID
<7vzlvlf4n9.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<477ED949.1030909@nrlssc.navy.mil>
Brandon Casey <casey@nrlssc.navy.mil> writes:
Show 17 quoted lines
> Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
> ---
>  builtin-reflog.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/builtin-reflog.c b/builtin-reflog.c
> index f422693..5e54989 100644
> --- a/builtin-reflog.c
> +++ b/builtin-reflog.c
> @@ -394,7 +394,7 @@ static int cmd_reflog_delete(int argc, const char **argv, const char *prefix)
>  		int recno;
>  
>  		if (!spec) {
> -			status |= error("Not a reflog: %s", ref);
> +			status |= error("Not a reflog: %s", argv[i]);
>  			continue;
>  		}

Bad Brandon! Looking at 'next' while everybody is asked to work on finding and fixing bugs on 'master' while -rc freeze.

Just kidding. Thanks, the code is obviously correct, and will queue.

I am not so surprised to see bugs in relatively new code that is only in 'next', especially this one that no Porcelains already use.

Previous: Brandon CaseyNext: Brandon Casey
Message 2 of 3 in “builtin-reflog.c: typo ref --> argv[i], could cause segfault”
  1. builtin-reflog.c: typo ref --> argv[i], could cause segfaultBrandon Casey, Jan 5, 2008
  2. Junio C HamanoJan 5, 2008
  3. Brandon CaseyJan 5, 2008

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.