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

Rik van Riel <[email protected]> writes:

> The problem is replying to an attachment.  The reason why having
> the patch in the main mail body is good is that it gets quoted
> by the email software and you can easily reply to individual
> parts of the patch.

If the attachment is "disposition=inline", does the problem still exist?
-- 
Krzysztof Halasa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

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

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

• Prev by Date: Re: [PATCH 2/3] add open iscsi netlink interface to iscsi transport class
• Next by Date: Re: /proc/ide/hd?/settings obsolete in 2.6.
• 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]