Re: [PATCH v3] fixup! refs: allow @{n} to work with n-sized reflog

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please disregard, I see that the fixup has already been included.

-Denton

On Mon, Jan 11, 2021 at 10:14:14PM -0800, Denton Liu wrote:
> Signed-off-by: Denton Liu <liu.denton@xxxxxxxxx>
> ---
>  refs.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/refs.c b/refs.c
> index e70dcd33f7..03968ad787 100644
> --- a/refs.c
> +++ b/refs.c
> @@ -906,7 +906,7 @@ static int read_ref_at_ent(struct object_id *ooid, struct object_id *noid,
>  	cb->date = timestamp;
>  
>  	/*
> -	 * It is not possible for cb->cnt == 0 on the first itertion because
> +	 * It is not possible for cb->cnt == 0 on the first iteration because
>  	 * that special case is handled in read_ref_at().
>  	 */
>  	if (cb->cnt > 0)
> -- 
> 2.30.0.284.gd98b1dd5ea
> 



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux