Re: [PATCH 1/4] sha1-lookup: add new "sha1_pos" function to efficiently lookup sha1

Reece Dunn [off-list ref] writes:

2009/4/5 Felipe Contreras [off-list ref]:

quoted

On Sun, Apr 5, 2009 at 9:59 PM, Junio C Hamano [off-list ref] wrote:

quoted

U3ZlcnJlIFJhYmJlbGllciA8c3JhYmJlbGllckBnbWFpbC5jb20+IHdyaXRlczoNCg0KPiBPbiBT
YXQsIEFwciA0LCAyMDA5IGF0IDIyOjU5LCBDaHJpc3RpYW4gQ291ZGVyIDxjaHJpc2Nvb2xAdHV4
ZmFtaWx5Lm9yZz4gd3JvdGU6DQo+PiArIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIMKgIMKgIGlmIChsbyA8PSBtaSAmJiBtaSA8IGhpKQ0KPj4gKyDCoCDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCDCoCBicmVhazsNCj4+ICsg
wqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgZGllKCJvb3BzIik7
DQo+DQo+IFRoYXQncyBnb2luZyB0byBiZSBhbiBvZmZpY2lhbCBnaXQgZXJyb3IgbWVzc2FnZT8g
V2h5IG5vdCBtYWtlIGl0ICJUaGUNCg0KSXQncyBub3QgImdvaW5nIHRvIGJlIiwgYnV0ICJoYXMg
YmVlbiBzbyBmb3IgdGhlIGxhc3QgdHdvIHllYXJzIHNpbmNlDQo1ZDIzZTEzIi4NCg0KSXQgaXMg
YW4gYXNzZXJ0LCBhbmQgSSB0aGluayBQZWZmJ3MgZGllKCJCVUc6IC4uLiIpIHdvdWxkIGJlIGEg
Z29vZCBpZGVhLg0K

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.

On Sun, Apr 05, 2009 at 01:02:30PM -0700, Junio C Hamano wrote:

quoted

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.

Actually, it is Sverre's fault. :)

You quoted his message, quoting Christian's message. Christian's message
was 7bit. But for some reason, Sverre's quoting of Christian's message
contains weird iso8859 space characters (0xa0).

But it is probably worth configuring Gnus to use QP instead of base64.
It's more efficient (for mostly ascii text), more readable to humans
looking at the encoded form, and is less likely to make you look like a
spammer. :)

-Peff

Heya,

On Sun, Apr 5, 2009 at 22:25, Jeff King [off-list ref] wrote:

Actually, it is Sverre's fault. :)

Fine, blame the Dutch, why not! :P

You quoted his message, quoting Christian's message. Christian's message
was 7bit. But for some reason, Sverre's quoting of Christian's message
contains weird iso8859 space characters (0xa0).

*points at GMail*, I ain't dun nothing funny! It's always been funny
WRT to vger and encoding issues though, so I'm not surprised.

-- 
Cheers,

Sverre Rabbelier

2009/4/5 Junio C Hamano [off-list ref]:

Reece Dunn [off-list ref] writes:

quoted

2009/4/5 Felipe Contreras [off-list ref]:

quoted

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:

quoted

+

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