From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] development flow
Date: Thu, 3 Sep 2009 14:06:48 +0800 [thread overview]
Message-ID: <200909031406.49008.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20090902061822.GA2503@lunn.ch>
On Wednesday 02 September 2009 14:18:22 Andrew Lunn wrote:
> We should post them to GregKH. That is what he said. What happens
> after that i don't know. Maybe he has an internal team which will do a
> review? Maybe it goes straight into staging and anybody who is
> interested can review the code.
>
> I would say the list needs to be open before we post the patches. We
> don't want valuable comments going lost, or annoying people who do
> reviews by bouncing there comments etc.
Ok, then who is doing the migration ? I surely can help to provide the list of
subscribed users.
> > It might be a good idea to maintain the ToDo list in the wiki - what do
> > you think ?
>
> I say the master has to be in the sources, where anybody who reviews
> staging will see. The Wiki copy is just a mirror, with a big comment
> that its not the master, all changes should first go into the sources
> TODO list which is then re-imported into the Wiki.
Fine with me.
> Maybe we need to branch SVN, or we setup a git tree. I already have
> local changes just so that it builds with linux-next.git from
> Saturday.
I can create git.open-mesh.com so that we have an official git to pull from ?
Regards,
Marek
next prev parent reply other threads:[~2009-09-03 6:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 1:36 [B.A.T.M.A.N.] [patch] adding subgraph-feature to vis-output in dot-file-format Linus Lüssing
2009-08-30 1:59 ` Linus Lüssing
2009-08-30 7:37 ` Andrew Lunn
2009-08-30 20:23 ` Simon Wunderlich
2009-08-31 5:26 ` [B.A.T.M.A.N.] development flow Marek Lindner
2009-08-31 5:50 ` Andrew Lunn
2009-09-01 18:47 ` Marek Lindner
2009-09-02 6:18 ` Andrew Lunn
2009-09-03 6:06 ` Marek Lindner [this message]
2009-09-08 16:01 ` Andrew Lunn
2009-09-08 17:54 ` [B.A.T.M.A.N.] mailing list migration (was: development flow) Marek Lindner
2009-09-18 21:14 ` Jacob Marble
2009-09-18 21:19 ` Jacob Marble
2009-09-19 7:59 ` Andrew Lunn
2009-09-28 3:29 ` Jacob Marble
2009-09-28 3:31 ` Jacob Marble
2009-09-28 5:03 ` Andrew Lunn
2009-09-28 6:12 ` Jacob Marble
2009-09-29 5:06 ` Jacob Marble
2009-09-29 5:25 ` Andrew Lunn
2009-09-29 9:19 ` Marek Lindner
2009-09-29 15:56 ` Jacob Marble
2009-09-29 16:14 ` Sven Eckelmann
2009-09-30 5:39 ` Jacob Marble
2009-09-30 19:27 ` Marek Lindner
2009-09-29 15:38 ` Jacob Marble
2009-08-30 19:55 ` [B.A.T.M.A.N.] [patch] adding subgraph-feature to vis-output in dot-file-format Simon Wunderlich
2009-08-30 20:15 ` Andrew Lunn
2009-08-30 21:47 ` Linus Lüssing
2009-08-31 5:28 ` Andrew Lunn
2009-09-01 20:47 ` Linus Lüssing
2009-09-04 18:58 ` Linus Lüssing
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=200909031406.49008.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
/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