From: Junio C Hamano <junkio@cox.net>
To: Peter Hagervall <hager@cs.umu.se>
Cc: junkio@cox.net, git@vger.kernel.org
Subject: Re: [PATCH] Sparse fix for builtin-diff
Date: Sun, 07 May 2006 13:43:26 -0700 [thread overview]
Message-ID: <7vpsiplg5t.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060507145046.GA24882@peppar.cs.umu.se> (Peter Hagervall's message of "Sun, 7 May 2006 16:50:47 +0200")
Peter Hagervall <hager@cs.umu.se> writes:
> You gotta love sparse:
>
> builtin-diff.c:88:4: error: Just how const do you want this type to be?
LOL.
> - const
> - const unsigned char *tmp_u;
> + const unsigned char *tmp_u;
I wondered how this bit snuck in, but it was like that
from the beginning, my bad.
Thanks.
prev parent reply other threads:[~2006-05-07 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 14:50 [PATCH] Sparse fix for builtin-diff Peter Hagervall
2006-05-07 20:43 ` Junio C Hamano [this message]
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=7vpsiplg5t.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=hager@cs.umu.se \
/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