All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Wolfe <dwolfe@lists.linuxppc.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Correct way to submit a patch?
Date: Tue, 5 Feb 2002 11:23:30 -0600	[thread overview]
Message-ID: <20020205112330.A28293@lists.linuxppc.org> (raw)
In-Reply-To: <20020205161852.GL32707@opus.bloom.county>; from trini@kernel.crashing.org on Tue, Feb 05, 2002 at 09:18:52AM -0700


[ Tom Rini writes: ]
> On Mon, Feb 04, 2002 at 02:25:03PM -0600, Dave Wolfe wrote:
> >
> > [ benh@kernel.crashing.org writes: ]
> > >
> > > The proper way is to send it to this list, eventually CC'ed to one
> > > of the people in the MAINTAINERS file depending which type of machine
> > > is affected by it.
> >
> > I would suggest that patches be attached to the email.
>
> Please don't...  I tend to take the Linus approach to this.  I won't
> ignore attachments like him tho.. :)

Then you risk mangled patches, and I guarantee that patches in the
archives will be unusable since they're converted to HTML. I'm not fond
of attachments either, but this is one application of them that is
appropriate.

--
 Dave Wolfe

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2002-02-05 17:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-04  7:43 Correct way to submit a patch? David Müller (ELSOFT AG)
2002-02-04  0:48 ` benh
2002-02-04 15:17   ` Tom Rini
2002-02-04 20:25   ` Dave Wolfe
2002-02-05 16:18     ` Tom Rini
2002-02-05 16:25       ` hollis
2002-02-05  9:04         ` Armin
2002-02-05 17:23       ` Dave Wolfe [this message]

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=20020205112330.A28293@lists.linuxppc.org \
    --to=dwolfe@lists.linuxppc.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.