Skip to contentSkip to conversation

Linux 2.6.0-test10

OT Junio C Hamano 3 participants 4 messages Nov 24, 2003 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"SB" == Stan Bubrouski <[email protected]> writes:

SB> The message by all indication is from Linus. I do not see the the lines SB> folded with '=' as you point out, but I do see the content-type as SB> charset ISO-8859-1, but I don't see Linus using Latin 1 as suspicious at SB> all. Finally someone more paranoid than me ;-)

I checked with http://marc.theaimsgroup.com/, and as you say there is no '=' folding. It could be done at fa.linux.kernel news gateway I use to read l-k..

#3 lore raw

Quote from Junio C Hamano <[email protected]>:

Quoted 10 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"SB" == Stan Bubrouski <[email protected]> writes:

SB> The message by all indication is from Linus. I do not see the the lines SB> folded with '=' as you point out, but I do see the content-type as SB> charset ISO-8859-1, but I don't see Linus using Latin 1 as suspicious at SB> all. Finally someone more paranoid than me ;-)

I checked with http://marc.theaimsgroup.com/, and as you say there is no '=' folding. It could be done at fa.linux.kernel news gateway I use to read l-k..

No, it _was_ in the raw mail from vger.kernel.org.

John.

#4 lore raw
Quoted 1 line · John Bradford

No, it _was_ in the raw mail from vger.kernel.org.

It's called mime encoding people. Thank you, please drive through.

--Ricky

#5 lore raw

Quote from Ricky Beam <[email protected]>:

Quoted 4 lines · John Bradford
Quoted 1 line

No, it _was_ in the raw mail from vger.kernel.org.

It's called mime encoding people. Thank you, please drive through.

I am aware what mime encoding is. I was just confirming that it was nothing to do with a broken gateway, which was suggested in a previous post.

John.