From: Joe Perches <joe@perches.com>
To: Larry Baker <baker@usgs.gov>
Cc: netdev@vger.kernel.org
Subject: Re: decnet: /proc/sys/net/decnet sysctl entries disappear
Date: Tue, 12 Feb 2013 11:15:34 -0800 [thread overview]
Message-ID: <1360696534.17456.4.camel@joe-AO722> (raw)
In-Reply-To: <6AA3F012-5843-4D66-AB3D-F8D40D458450@usgs.gov>
On Tue, 2013-02-12 at 10:58 -0800, Larry Baker wrote:
> The instructions say "e-mail that person". There are only two persons
> listed as decnet maintainers, one of which has told me she is not
> involved much any more. The instructions only mention sending to
> mailing lists if the maintainer does not respond.
>
> I explicitly followed the instructions.
I think you need to read a little farther.
> If the developers want mailing lists CC'd right off the bat, the instructions should be updated.
from: Documentation/SubmittingPatches
6) Select your CC (e-mail carbon copy) list.
Unless you have a reason NOT to do so, CC linux-kernel@vger.kernel.org.
next prev parent reply other threads:[~2013-02-12 19:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 0:26 decnet: /proc/sys/net/decnet sysctl entries disappear Larry Baker
2013-02-12 0:46 ` Ben Hutchings
2013-02-12 1:01 ` Ben Hutchings
2013-02-12 1:30 ` Larry Baker
2013-02-12 1:09 ` David Miller
2013-02-12 18:16 ` Larry Baker
[not found] ` <8EAAA907-914A-4670-BAAF-ABC95C0838CA@usgs.gov>
[not found] ` <20130211.235347.25383457019933412.davem@davemloft.net>
2013-02-12 18:28 ` Larry Baker
2013-02-12 18:43 ` Joe Perches
2013-02-12 18:58 ` Larry Baker
2013-02-12 19:15 ` Joe Perches [this message]
2013-02-12 18:55 ` Ben Hutchings
2013-02-12 22:13 ` PROBLEM: decnet: /proc/sys/net/decnet sysctl entries disappear (2.6.27 through 3.3.x) Larry Baker
[not found] ` <456F0392-03CE-4207-A092-F890D530B746@usgs.gov>
[not found] ` <877gmca8qb.fsf@xmission.com>
2013-02-14 0:50 ` decnet: /proc/sys/net/decnet sysctl entries disappear Larry Baker
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=1360696534.17456.4.camel@joe-AO722 \
--to=joe@perches.com \
--cc=baker@usgs.gov \
--cc=netdev@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