Re: [PATCH] Fix buggy ref recording

From: Junio C Hamano <junkio@cox.net>
Date: Sep 23, 2006, 00:44 UTC
Message-ID: <7vzmcrxvgw.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20060922230845.GB8259@pasky.or.cz>

Petr Baudis <pasky@suse.cz> writes:

> And since just reporting it did not magically result in a fix... ;-)

Yes, please always send in a patch to be applied to get the attribution right.

I've never seen you send out a corrupt patch over e-mail. What's different this time?

Show 8 quoted lines

> diff --git a/refs.c b/refs.c
> index 40f16af..5fdf9c4 100644
> --- a/refs.c
> +++ b/refs.c
> @@ -472,7 +472,7 @@ static struct ref_lock *lock_ref_sha1_ba
>
>  	lock->ref_name = xstrdup(ref);
>  	lock->log_file = xstrdup(git_path("logs/%s", ref));

The empty line at the beginning of the hunk is totally empty, not even with a SP to show it is a context line.

Will hand-apply, no need to resend.