Re: source control management for Octave

[Paul Kienzle]

On Oct 17, 2005, at 9:54 PM, Andy Adler wrote:

> In order to allow testing of SVN for octave, Stefan van der Walt
> and I have set up a server with a svn octave repository.
>
> I sample usage is:
>  $ svn ls svn+ssh://address@hidden/octave/
>   branches/
>   tags/
>   trunk/
>
> At this point, I would like to know how this should be used.
>
> One option would be for developers who wish to use this
> machine to send me their ssh public key. They will then
> have read/write access.
>
> Should I do this?

I notice that you can have different access controls for different
parts of the repository.

        http://svnbook.red-bean.com/en/1.0/ch06s04.html#svn-ch-6-sect-4.4.2

Do we want to gather the various octave related projects under one
roof, such as octave-forge, octaviz, etc.?

The main reason I can see for doing so is that it will make it easier
for John to move functions and packages in and out of the core without
losing the change history.

This will make more work for the server administrator though.

- Paul