From: Rick Jones <rick.jones2@hp.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
netdev@vger.kernel.org
Subject: Re: [RFC] Any value in having a netdev FAQ?
Date: Thu, 18 Jul 2013 10:53:53 -0700 [thread overview]
Message-ID: <51E82BB1.7090605@hp.com> (raw)
In-Reply-To: <1374112504.7622.49.camel@envy.home>
On 07/17/2013 06:55 PM, Darren Hart wrote:
> On Mon, 2013-07-15 at 22:59 -0400, Paul Gortmaker wrote:
>
>> IMPORTANT: Do not send new net-next content to netdev during the
>> period during which net-next tree is closed.
>>
>> Shortly after the two weeks have passed, (and vX.Y-rc1 is released) the
>> tree for net-next reopens to collect content for the next (vX.Y+1) release.
>
yesterday I tried to send an email to Jeremy Kerr asking if there was
some way to tweak patchwork to allow DaveM a way to signal net-next
being closed - perhaps some message at
http://patchwork.ozlabs.org/project/netdev/list/ Baring that, I
wondered if it would be possible to submit a dummy "[PATCH net-next]
net-next closed until futher notice" patch, and fake-out the date to be
some point in the future, so it would appear at the top of the list of
patches.
rick jones
next prev parent reply other threads:[~2013-07-18 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 2:59 [RFC] Any value in having a netdev FAQ? Paul Gortmaker
2013-07-16 20:05 ` David Miller
2013-07-16 20:34 ` Darren Hart
2013-07-16 20:35 ` Darren Hart
2013-07-17 15:08 ` Paul Gortmaker
2013-07-16 20:32 ` Darren Hart
2013-07-17 15:18 ` Paul Gortmaker
2013-07-17 15:56 ` Joe Perches
2013-07-18 18:21 ` Benjamin Poirier
2013-07-16 20:42 ` Joe Perches
2013-07-18 1:55 ` Darren Hart
2013-07-18 13:33 ` Paul Gortmaker
2013-07-18 17:53 ` Rick Jones [this message]
2013-07-18 2:32 ` Hannes Frederic Sowa
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=51E82BB1.7090605@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=dvhart@linux.intel.com \
--cc=gregkh@linuxfoundation.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 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.