From: Rob Landley <rob@landley.net>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: [PATCH net-next] Documentation: add networking/netdev-FAQ.txt
Date: Sun, 04 Aug 2013 21:34:11 -0500 [thread overview]
Message-ID: <1375670051.8422.6@driftwood> (raw)
In-Reply-To: <1375298180-17628-1-git-send-email-paul.gortmaker@windriver.com> (from paul.gortmaker@windriver.com on Wed Jul 31 14:16:20 2013)
On 07/31/2013 02:16:20 PM, Paul Gortmaker wrote:
> A collection of expectations and operational details about how
> networking development takes place in the context of the netdev
> mailing list.
http://vger.kernel.org has 149 mailing lists, and that's maybe half of
the kernel lists out there. (The linux foundation's got a bunch, the
device tree list just switched servers, etc.)
Why is this list special?
> +++ b/Documentation/networking/netdev-FAQ.txt
> @@ -0,0 +1,224 @@
> +
> +Information you need to know about netdev
> +-----------------------------------------
> +
> +Q: What is netdev?
> +
> +A: It is a mailing list for all network related linux stuff. This
> includes
> + anything found under net/ (i.e. core code like IPv6) and
> drivers/net
> + (i.e. hardware specific drivers) in the linux source tree.
I'm all for having this somewhere, but this is a silly place for it.
Putting it in linux/Documentation means you'll frequently tell newbies
"read the FAQ, except it's not on the web, we stuck it in a
subdirectory of a sudirectory of the kernel source because that's the
obvious place to stick the FAQ for a mailing list".
Rob
next prev parent reply other threads:[~2013-08-05 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 19:16 [PATCH net-next] Documentation: add networking/netdev-FAQ.txt Paul Gortmaker
2013-08-01 0:37 ` David Miller
2013-08-05 2:34 ` Rob Landley [this message]
2013-08-05 2:36 ` David Miller
2013-10-19 17:13 ` Randy Dunlap
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=1375670051.8422.6@driftwood \
--to=rob@landley.net \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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).