Re: [PATCH 1/4] sha1-lookup: add new "sha1_pos" function to efficiently lookup sha1
- From
Jay Soffian <jaysoffian@gmail.com>
- Date
- Apr 5, 2009, 20:34 UTC
- Message-ID
- <76718490904051334p67e34ee5t89e73430a311bff3@mail.gmail.com>
- In-Reply-To
- <3f4fd2640904051231x17117a4g3efe38067c8d3359@mail.gmail.com>
On Sun, Apr 5, 2009 at 3:31 PM, Reece Dunn <msclrhd@googlemail.com> wrote:
Show 17 quoted lines
> 2009/4/5 Felipe Contreras <felipe.contreras@gmail.com>: >> On Sun, Apr 5, 2009 at 9:59 PM, Junio C Hamano <gitster@pobox.com> wrote: >>> 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 :)!
Junio's _original_ message was fine. The problem is that vger (majordomo) appends the mailing list footer which technically corrupts the message. Respectable MUA's can deal with the corruption, but gmail's web-interface just shows the raw base64 (previously it used to just show an empty message). I've filed a bug against gmail, but who knows.
The other options are:
- fix majordomo on vger - replace majordomo on vger with a decent MLM - disable the mailing list footer - deal with it if you're a gmail user
j.