From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: netdev: patchwork.ozlabs.org vs patchwork.kernel.org ?
Date: Wed, 13 Jan 2010 17:49:04 -0800 [thread overview]
Message-ID: <1263433744.1966.52.camel@Joe-Laptop.home> (raw)
In-Reply-To: <20100113.174141.169192840.davem@davemloft.net>
On Wed, 2010-01-13 at 17:41 -0800, David Miller wrote:
> From: Joe Perches <joe@perches.com>
> Date: Wed, 13 Jan 2010 17:40:37 -0800
> > On Wed, 2010-01-13 at 17:32 -0800, David Miller wrote:
> >> Encoding your patches as base64 binary octet stream attachments
> >> causes them to get missed by our automated patch tracking system:
> >> http://patchwork.ozlabs.org/project/netdev/list/
> > What is the reason why netdev doesn't use patchwork.kernel.org?
> > It seems odd that it doesn't. Odd like the arm mailing lists.
> ozlabs was the original, and so just like powerpc port that's where we
> started using the tool.
> I honestly don't care where it's hosted.
Neither do I, but it might be nice to put a link
to the patchwork.ozlabs.org queues on this page
http://patchwork.kernel.org/
(or the other way 'round, or both)
so there's a centralized listing of all linux related
patchwork queues.
next prev parent reply other threads:[~2010-01-14 1:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 17:25 [PATCH 1/2] net: at91_ether.c - Allow transmitter interrupt to be handled first in ISR James Kosin
2010-01-14 1:32 ` David Miller
2010-01-14 1:40 ` netdev: patchwork.ozlabs.org vs patchwork.kernel.org ? Joe Perches
2010-01-14 1:41 ` David Miller
2010-01-14 1:49 ` Joe Perches [this message]
2010-01-14 20:28 ` [PATCH 1/2] net: at91_ether.c - Allow transmitter interrupt to be handled first in ISR James Kosin
2010-01-15 5:38 ` Eric Dumazet
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=1263433744.1966.52.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).