From: benh@kernel.crashing.org
To: linuxppc-dev@lists.linuxppc.org, "David Müller " <d.mueller@elsoft.ch>
Subject: Re: Correct way to submit a patch?
Date: Mon, 4 Feb 2002 01:48:49 +0100 [thread overview]
Message-ID: <20020204004850.24542@mailhost.mipsys.com> (raw)
In-Reply-To: <3C5E3B8F.5060105@elsoft.ch>
>Hi
>
>I was wondering what's the correct, proposed way to submit a patch to the
>LinuxPPC kernel tree so the patch surely reaches the responsible person
>and gets
>the necessary attention.
>
>What about a special linuxppc-patch mailing list ?
>What about a patch tracking system like ARM Linux is using it
>http://www.arm.linux.org.uk/developer/patches/ ?
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.
We used to have a patch tracker on sourceforge, but we never really
used the way we should have.
Behave with us (PPC maintainers) like you would do with Linus: send us
patches and if it gets ingnored after a while, assume we lost the mail ;)
Unlike Linus, we tend to reply if for some reason we don't want to
apply the patch.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-04 0:48 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 [this message]
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
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=20020204004850.24542@mailhost.mipsys.com \
--to=benh@kernel.crashing.org \
--cc=d.mueller@elsoft.ch \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).