[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: source control management for Octave

From: Paul Kienzle
Subject: Re: source control management for Octave
Date: Mon, 17 Oct 2005 22:35:03 -0400

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/

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.


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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]