Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] builtin-reflog.c: typo ref --> argv[i], could cause segfault
Date: Fri, 04 Jan 2008 17:22:02 -0800	[thread overview]
Message-ID: <7vzlvlf4n9.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <477ED949.1030909@nrlssc.navy.mil> (Brandon Casey's message of "Fri, 04 Jan 2008 19:11:37 -0600")

Brandon Casey <casey@nrlssc.navy.mil> writes:

> 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.

  reply	other threads:[~2008-01-05  1:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-05  1:11 [PATCH] builtin-reflog.c: typo ref --> argv[i], could cause segfault Brandon Casey
2008-01-05  1:22 ` Junio C Hamano [this message]
2008-01-05  1:35   ` Brandon Casey

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=7vzlvlf4n9.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=casey@nrlssc.navy.mil \
    --cc=git@vger.kernel.org \
    /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