From: Joe Perches <joe@perches.com>
To: Pravin B Shelar <pshelar@nicira.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] MAINTAINERS: Update Open vSwitch entry.
Date: Fri, 02 Jan 2015 10:41:17 -0800 [thread overview]
Message-ID: <1420224077.23591.2.camel@perches.com> (raw)
In-Reply-To: <1420223098-1591-1-git-send-email-pshelar@nicira.com>
On Fri, 2015-01-02 at 10:24 -0800, Pravin B Shelar wrote:
> OVS development is moved to netdev mailing list. Update tree and
> list in MAINTAINERS file.
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -7008,9 +7008,11 @@ F: arch/openrisc/
>
> OPENVSWITCH
> M: Pravin Shelar <pshelar@nicira.com>
> +L: netdev@vger.kernel.org
> L: dev@openvswitch.org
> W: http://openvswitch.org
> -T: git git://git.kernel.org/pub/scm/linux/kernel/git/pshelar/openvswitch.git
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
> S: Maintained
> F: net/openvswitch/
>
Are those git entries really appropriate?
next prev parent reply other threads:[~2015-01-02 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 18:24 [PATCH net-next] MAINTAINERS: Update Open vSwitch entry Pravin B Shelar
2015-01-02 18:41 ` Joe Perches [this message]
2015-01-02 18:54 ` Pravin Shelar
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=1420224077.23591.2.camel@perches.com \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.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