Re: [PATCH 1/4] sha1-lookup: add new "sha1_pos" function to efficiently lookup sha1
- From
- Reece Dunn <msclrhd@googlemail.com>
- Date
- Apr 5, 2009, 20:39 UTC
- Message-ID
- <3f4fd2640904051339h8d31d73t40d79b03ba121e1c@mail.gmail.com>
- In-Reply-To
- <7vocvaq36x.fsf@gitster.siamese.dyndns.org>
2009/4/5 Junio C Hamano <gitster@pobox.com>:
Show 11 quoted lines
> Reece Dunn <msclrhd@googlemail.com> writes: > >> 2009/4/5 Felipe Contreras <felipe.contreras@gmail.com>: >>> >>> Huh? >> >> I think Junio is trying to learn base64 :)! > > I think that is what my Gnus/message-mode did. I do not know which letter > triggered it to decide it is UTF-8 to begin with, though. As far as I am > aware, I didn't type anything non-ascii in my message.
Ok, so digging a little deeper, `base64 -d | od -t x1` gives the following (partial) output:
0000200 6f 74 65 3a 0d 0a 3e 3e 20 2b 20 c2 a0 20 c2 a0
The key entry here is the a0 character (NO-BREAK SPACE) or NBSP.
This is at: $ base64 -d test | od -t x1 | grep a0 | head -n 1 | xxd -r ote:
>> +
So looks like it is in the patch you are quoting. NOTE: I have removed the spaces after the +. Also, according to www.unicode.org, c2 is A^ (A with a circumflex) -- not sure what that is doing there, though.
- Reece