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

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....

Attachment: pgpztxQfDu6Jh.pgp
Description: PGP signature

---

• Follow-Ups:
  • Re: [RFC][PATCH] update SubmittingPatches to clarify attachment policy
    • From: Dave Hansen <[email protected]>

• References:
  • [RFC][PATCH] update SubmittingPatches to clarify attachment policy
    • From: Dave Hansen <[email protected]>

• Prev by Date: [PATCH] device-mapper: Some missing statics
• Next by Date: Re: [RFC][PATCH] update SubmittingPatches to clarify attachment policy
• Previous by thread: Re: [RFC][PATCH] update SubmittingPatches to clarify attachment policy
• Next by thread: Re: [RFC][PATCH] update SubmittingPatches to clarify attachment policy
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]