From: Krzysztof Halasa <khc@pm.waw.pl>
To: Rik van Riel <riel@redhat.com>
Cc: Dave Hansen <haveblue@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] update SubmittingPatches to clarify attachment policy
Date: Thu, 05 May 2005 12:06:55 +0200 [thread overview]
Message-ID: <m38y2uoukg.fsf@defiant.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0505042109020.18390@chimarrao.boston.redhat.com> (Rik van Riel's message of "Wed, 4 May 2005 21:09:49 -0400 (EDT)")
Rik van Riel <riel@redhat.com> 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
next prev parent reply other threads:[~2005-05-05 10:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 17:01 Dave Hansen
2005-05-04 17:10 ` Jon Smirl
2005-05-04 17:54 ` Jan-Benedict Glaw
2005-05-04 18:23 ` Richard B. Johnson
2005-05-05 8:12 ` Jan-Benedict Glaw
2005-05-05 16:43 ` Lee Revell
2005-05-05 17:31 ` Jan-Benedict Glaw
2005-05-04 20:42 ` Rafael J. Wysocki
2005-05-04 17:15 ` Dmitry Torokhov
2005-05-04 17:16 ` Valdis.Kletnieks
2005-05-04 17:25 ` Dave Hansen
2005-05-04 17:55 ` Chris Wright
2005-05-04 18:14 ` Dave Hansen
2005-05-04 19:21 ` Alexander Nyberg
2005-05-05 19:06 ` Jeff Garzik
2005-05-04 17:58 ` Dipankar Sarma
2005-05-04 18:52 ` Krzysztof Halasa
2005-05-04 19:28 ` Randy.Dunlap
2005-05-14 22:10 ` Domen Puncer
2005-05-04 17:59 ` John W. Linville
2005-05-05 1:09 ` Rik van Riel
2005-05-05 9:07 ` Geert Uytterhoeven
2005-05-05 10:06 ` Krzysztof Halasa [this message]
2005-05-05 12:01 ` Paulo Marques
2005-05-05 21:34 ` Steven Cole
2005-05-06 1:31 ` Lee Revell
2005-05-06 4:05 ` Valdis.Kletnieks
[not found] <40vxU-1a1-25@gated-at.bofh.it>
[not found] ` <40vRd-1os-1@gated-at.bofh.it>
2005-05-05 2:36 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38y2uoukg.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®