Raymond Toy <toy.raymond at gmail.com> writes:
> On 1/30/11 11:40 PM, Robert Dodier wrote:
>> On 1/30/11, Raymond Toy <toy.raymond at gmail.com> wrote:
>>
>>> One item that I wanted to point out is that Sourceforge is considering
>>> the end-of-life of the CVS service. There's no timeline given, but this
>>> does affect maxima since maxima is currently using CVS. I suppose we
>>> should consider moving to another version control system sometime soon.
>>> (Other than the occasional downtime, I've been quite happy with CVS even
>>> if it is old and crusty. I don't really want to learn yet another
>>> system, but it seems we might be forced to.)
>> Well, there have been suggestions to use some other system --
>> I think git and maybe subversion have been mentioned.
>> I don't care too much one way or another.
>> I guess at this point I wouldn't mind switching to git.
> I notice that clisp (also hosted on sourceforge) wants to move to hg
> (mercurial). Perhaps a distributed version control system like git or
> hg would be best. But I think subversion probably has the lowest
> learning curve if you're already familiar with cvs. I have used the
> others a very little. Only to get the latest version of something.
Since I'm not particularly active on this list, the last thing I want to
do is have my only post being a git vs. hg vs. CVS vs... flame. But...
Git is much more complicated than CVS. But it's not more complicated for
the "end users": either those committing to the project or those pulling
it. For the committer, the typical usage looks like
git status
# Ooh, I changed some stuff.
git add foo.lisp bar.lisp
git commit
# Type a commit message in the editor that appears
git push
For the person pulling from the tree just to build:
git clone git://someurl
./configure && make && make install
and then when they update:
git pull
Of course, there are more ways to do things, but my point is that it's
easy.
Now, you can also do clever things, which weren't possible with
CVS. Doing these is somewhat complicated. But the things themselves are
also complicated, so maybe this isn't a problem. Also bear in mind that
git's very popular. As such, there are an awful lot of tutorials
floating around for how to do semi-complicated things.
That's just my 2 pence. Incidentally, at least I (and probably others)
have been converting the maxima tree to git on the fly for a while,
since it's much easier to work with and see what changed when. In case
you're worried about bloat in the amount one has to store locally, my
.git folder (which holds *all* the commit history of the project) is
40mb or so.
Rupert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 315 bytes
Desc: not available
URL: <http://www.math.utexas.edu/pipermail/maxima/attachments/20110131/cb52ce3e/attachment.pgp>;