From: Oliver Hartkopp <socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
To: Marc Kleine-Budde <mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
Cc: socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
Urs Thuermann
<urs-5sm3ckEb1NlYFmeL5InDC7NAH6kLmebB@public.gmane.org>,
"linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [RFC PATCH] CAN MAINTAINERS
Date: Fri, 02 Dec 2011 09:46:08 +0100 [thread overview]
Message-ID: <4ED89050.3040201@hartkopp.net> (raw)
In-Reply-To: <4ED75EED.6010009-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
On 01.12.2011 12:03, Marc Kleine-Budde wrote:
> On 12/01/2011 11:49 AM, Oliver Hartkopp wrote:
>> As the net tree only get's fixes i wonder why we should clone that tree?
>> Working directly on Dave's net-tree for fixes looks straight forward to me.
>
> Thinking about it - yes, what about just keeping linux-can-next.
>
>> But the idea for a linux-can-next is great.
>>
>> This would settle the process that we discuss new drivers & changes on
>> linux-can ML and finally commit the stuff in linux-can-next, where one of us
>> can send a pull request to Dave.
>
> ...you send the pull request.
>
>> So everything beyond fixes would go this way then.
>
> +1
>
> So we communicate to davem that we now have a git tree, and Oliver is
> the one that send the pull requests. Let's ask him if he wants to see
> the patches in the pull request.
Hey Marc,
i'm not as good as you using git. Indeed i'm a git newbie and do not have the
time right now to get in that deep that i dare to post correct pull requests
to netdev.
Following the hints from Dave i checked the MAINTAINERS file how the wireless
guys handle their subsystem in detail. Regarding John Linville, who's
collecting all the stuff from several people to send finally push requests to
Dave i would suggest that you become our 'John Linville for CAN'.
You speak git fluently and you know the project very good - so my suggestion
to clean up the MAINTAINTERS file is this:
diff --git a/MAINTAINERS b/MAINTAINERS
index 717d9e9..af8a0a9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1707,11 +1707,8 @@ F: arch/x86/include/asm/tce.h
CAN NETWORK LAYER
M: Oliver Hartkopp <socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
-M: Oliver Hartkopp <oliver.hartkopp-l29pVbxQd1IUtdQbppsyvg@public.gmane.org>
-M: Urs Thuermann <urs.thuermann-l29pVbxQd1IUtdQbppsyvg@public.gmane.org>
L: linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-L: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-W: http://developer.berlios.de/projects/socketcan/
+W: http://gitorious.org/linux-can
S: Maintained
F: net/can/
F: include/linux/can.h
@@ -1723,8 +1720,7 @@ F: include/linux/can/gw.h
CAN NETWORK DRIVERS
M: Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
L: linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-L: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
-W: http://developer.berlios.de/projects/socketcan/
+W: http://gitorious.org/linux-can
S: Maintained
F: drivers/net/can/
F: include/linux/can/dev.h
@@ -4587,6 +4583,17 @@ F: include/linux/wireless.h
F: include/net/iw_handler.h
F: drivers/net/wireless/
+NETWORKING [CAN]
+M: Marc Kleine-Budde <mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
+L: linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
+W: http://gitorious.org/linux-can
+T: git://gitorious.org/linux-can/linux-can.git
+T: git://gitorious.org/linux-can/linux-can-next.git
+S: Maintained
+F: net/can/
+F: drivers/net/can/
+F: include/linux/can*
+
NETWORKING DRIVERS
L: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
W: http://www.linuxfoundation.org/en/Net
Regards,
Oliver
next prev parent reply other threads:[~2011-12-02 8:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48E9EDF6.4000009@pengutronix.de>
2011-11-30 22:55 ` git-tree, NOW! Marc Kleine-Budde
[not found] ` <4ED6B460.2010508-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-12-01 8:04 ` Wolfgang Grandegger
[not found] ` <4ED7351E.2010907-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-01 9:16 ` Marc Kleine-Budde
[not found] ` <4ED745F6.8030302-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-12-01 9:30 ` Wolfgang Grandegger
[not found] ` <4ED7494F.6080603-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-01 9:37 ` Marc Kleine-Budde
2011-12-01 10:49 ` Oliver Hartkopp
2011-12-01 11:03 ` Marc Kleine-Budde
[not found] ` <4ED75EED.6010009-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-12-02 8:46 ` Oliver Hartkopp [this message]
[not found] ` <4ED89050.3040201-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2011-12-02 12:22 ` [RFC PATCH] CAN MAINTAINERS Marc Kleine-Budde
2011-12-02 12:34 ` Wolfgang Grandegger
2011-12-02 13:15 ` Oliver Hartkopp
[not found] ` <4ED8CF58.3010109-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2011-12-02 13:34 ` Wolfgang Grandegger
2011-12-02 13:55 ` Oliver Hartkopp
[not found] ` <4ED8C5D8.6000505-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-02 14:08 ` Marc Kleine-Budde
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=4ED89050.3040201@hartkopp.net \
--to=socketcan-fj+pqtutwrtk1umjsbkqmq@public.gmane.org \
--cc=linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=urs-5sm3ckEb1NlYFmeL5InDC7NAH6kLmebB@public.gmane.org \
--cc=wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.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).