From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Thu, 3 Sep 2009 14:06:48 +0800 References: <20090830013647.GA26017@Linus-Debian> <200909020247.06730.lindner_marek@yahoo.de> <20090902061822.GA2503@lunn.ch> In-Reply-To: <20090902061822.GA2503@lunn.ch> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200909031406.49008.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] development flow Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking 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