From: Marc Kleine-Budde <mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
Cc: socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
Oliver Hartkopp
<socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>,
Urs Thuermann
<urs-5sm3ckEb1NlYFmeL5InDC7NAH6kLmebB@public.gmane.org>,
"linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC PATCH] CAN MAINTAINERS
Date: Fri, 02 Dec 2011 15:08:06 +0100 [thread overview]
Message-ID: <4ED8DBC6.4050207@pengutronix.de> (raw)
In-Reply-To: <4ED8C5D8.6000505-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 806 bytes --]
On 12/02/2011 01:34 PM, Wolfgang Grandegger wrote:
>>> You speak git fluently and you know the project very good - so my suggestion
>>> to clean up the MAINTAINTERS file is this:
>>
>> The cleanups look got, however, do we need the linux-can tree. Do the
>> wireless people have two trees?
>
> I would drop it for the time being.
The wireless people have two trees:
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless.git
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next.git
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
[-- Attachment #2: Type: text/plain, Size: 188 bytes --]
_______________________________________________
Socketcan-core mailing list
Socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
https://lists.berlios.de/mailman/listinfo/socketcan-core
prev parent reply other threads:[~2011-12-02 14:08 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 ` [RFC PATCH] CAN MAINTAINERS Oliver Hartkopp
[not found] ` <4ED89050.3040201-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2011-12-02 12:22 ` 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 [this message]
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=4ED8DBC6.4050207@pengutronix.de \
--to=mkl-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@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).