From: "David Müller (ELSOFT AG)" <d.mueller@elsoft.ch>
To: linuxppc-dev@lists.linuxppc.org
Subject: Correct way to submit a patch?
Date: Mon, 04 Feb 2002 08:43:11 +0100 [thread overview]
Message-ID: <3C5E3B8F.5060105@elsoft.ch> (raw)
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/ ?
Dave
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-02-04 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-04 7:43 David Müller (ELSOFT AG) [this message]
2002-02-04 0:48 ` Correct way to submit a patch? 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
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=3C5E3B8F.5060105@elsoft.ch \
--to=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 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.