Re: [RFC][PATCH] update SubmittingPatches to clarify attachment policy

[Dipankar Sarma <dipankar@in.ibm.com>]

On Wed, May 04, 2005 at 10:25:16AM -0700, Dave Hansen wrote:
> On Wed, 2005-05-04 at 13:16 -0400, Valdis.Kletnieks@vt.edu wrote:
> > On Wed, 04 May 2005 10:01:56 PDT, Dave Hansen said:
> > 
> > > -6) No MIME, no links, no compression, no attachments.  Just plain text.
> > > +6) No MIME, no links, no compression.  Just plain text.
> > 
> > Logically buggy.  You can't have an attachment without the MIME markup that
> > *says* it's an attachment.  I think what you meant was "No Content-Type-Encoding":
> > i.e. 'none' is acceptable, but 'quoted-printable' (which causes all the
> > spurious =20 and =3D you sometimes see) and 'base64' (uuencode on steroids)
> > aren't....
> 
> Thanks for pointing out my flawed logic.  I wasn't quite sure what was
> MIME and what wasn't.  How about the attached patch, instead?

I don't like it, but that is only because your mailer sends
them as test/x-patch and my mailer cannot quote the patch in reply :)

Thanks
Dipankar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/