[Top][All Lists]

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

source control management for Octave

From: Stefan van der Walt
Subject: source control management for Octave
Date: Wed, 5 Oct 2005 18:37:20 +0200
User-agent: Mutt/1.5.6+20040907i


Octave is currently being hosted in CVS -- but is there any reason why
we couldn't move over to Subversion?

The reason I ask, is because CVS makes it very difficult to work on
projects when you have a slow network connection.  To do simple
operations like "log" or "diff" requires an internet connection -- for
no good reason.

Subversion does not only address this problem, but a few others too
(for a more complete list see http://svnbook.red-bean.com/en/1.1/apa.html):

* Directories are managed
* Commits are atomic
* Secure access can be given to developers
  See http://www.chiark.greenend.org.uk/~sgtatham/svn.html

I am not sure whether any users currently have access to the
repository.  If none, then I would suggest an alternative option:

If Octave is hosted in Mercurial, I can have a local repository on my
machine.  This means that I could work on complicated changes, and
pull your changes every day -- handling conflicts as they arise.  Once
I am done, I could simply export all the changes, and send it to you
either as a bundle or a patch.

If we opt for Mercurial, we do not need to lose the history.  'Tailor'
can be used to convert the current CVS repository (with all logs) to

Whether Subversion or Mercurial, either would be a vast improvement
over CVS.


reply via email to

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