public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dipankar Sarma <dipankar@in.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Valdis.Kletnieks@vt.edu,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] update SubmittingPatches to clarify attachment policy
Date: Wed, 4 May 2005 23:28:07 +0530	[thread overview]
Message-ID: <20050504175807.GA5445@in.ibm.com> (raw)
In-Reply-To: <1115227516.22718.4.camel@localhost>

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

  parent reply	other threads:[~2005-05-04 18:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04 17:01 [RFC][PATCH] update SubmittingPatches to clarify attachment policy 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 [this message]
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
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=20050504175807.GA5445@in.ibm.com \
    --to=dipankar@in.ibm.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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