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,
"linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: git-tree, NOW!
Date: Thu, 01 Dec 2011 10:16:38 +0100 [thread overview]
Message-ID: <4ED745F6.8030302@pengutronix.de> (raw)
In-Reply-To: <4ED7351E.2010907-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1922 bytes --]
On 12/01/2011 09:04 AM, Wolfgang Grandegger wrote:
>> I think we need a git tree. It's the second time our humble network
>> maintainer merged some patches to early. IMHO both times related to bad
>> communication.......
>
> What do you mean? Usually we do not communicate anything to Dave for the
> normal v1->v2->v3->... review and patch update process (this does not
> excuse the bad quality of my last series). The problem is that it's not
> easy for him to follow our work and therefore we need our own GIT tree.
Yes - exactly. I think we're meaning the same:
It's hard to figure out for him when a series is "ready", (or at least
we think it is). We haven't communicated a "series is still in review"
nor a "series is now ready".
I like Oliver's remark to first keep the discussion on the linux-can
mailinglist and post the "final" series on netdev.
> That's also what Dave asks for. Apart from the tree he asks for someone
> who acts as the one and only interface to him.
Yes, technically that could/should be the git tree, in persona Wolfgang
or/and (as Dave asked for one person) Oliver.
>> I've setup a git repo on gitorious:
>>
>> https://gitorious.org/linux-can/linux-can
>>
>> It's based on net-next, and currently David's net-next/master is pushing
>> there. It probably takes some time, the box pushing has just 4 mbit/s
>> upstream.
>>
>> Comments?
>
> Apart from net-next, we may also need the net tree (as branch?).
During merge windows David merges into his net-next tree, anyway I can
setup linux-can and linux-can-next, based on the linux-net and
linux-net-next trees.
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
next prev parent reply other threads:[~2011-12-01 9:16 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 [this message]
[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
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=4ED745F6.8030302@pengutronix.de \
--to=mkl-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=socketcan-core-0fE9KPoRgkgATYTw5x5z8w@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).