On Tue, Feb 7, 2012 at 9:22 AM, Jeremy Bennett <[email protected]> wrote: > I wish to propose that user Anantha ([email protected]) be given > write access to SVN. > > Anantha has offered to extend Or1ksim to explicitly support and enforce > Harvard architectures, by allowing memories to be restricted to > data-only or instruction-only access. > > Anantha will carry out this work on a separate branch, which can be > merged into Or1ksim on completion.
Welcome Anantha, > > Our current working procedure is that any non-obvious SVN commits must > be posted to the mailing list for review before committing. > > I should like to modify that to allow commits to non-release branches > without review. This will allow projects like that proposed to Anantha > to proceed quickly on their own branches. They only will need mailing > list review when they are merged into HEAD (or a release branch). > Yes, this sounds sensible. I think this is a good approach so that work people might be doing on a branch is a bit more immediately visible, instead of them having a separate repository elsewhere. But on this point (perhaps a little unrelated) I think it might be useful to have a links page on the wiki with a list of branched developments and their location. It's not essential, but it might help someone reviewing what work is in progress find things which aren't hosted on the OpenCores SVN. Cheers, Julius _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
