Re: [B.A.T.M.A.N.] development flow

Marek Lindner
2009-09-03T06:06:48Z

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