Re: git or svn

[Taco Hoekwater <taco@elvenkind.com>]

On Sep 27, 2013, at 9:01 AM, Peter Münster <pmlists@free.fr> wrote:

> On Fri, Sep 27 2013, Aditya Mahajan wrote:
> 
>> The last time I tried, merging multiple version in svn is a huge pain. One of
>> the advantages of DVCS is that branching and merging are easy.
> 
> I understand. Please go ahead if you need git. My preference for svn is
> just my personal opinion, coming from my personal experience: people
> wanted to change a well running system, using the latest and greatest
> tools. In the end, after quite some efforts, there was no benefit, it
> was just a bit more complicated.

+1 from me: I have exactly the same experience personally.

> I'm just lucky doing my 3 svn-commits per year, and with git I would
> do git-commits.


+1 again.

The manual is on supelec because that is where the metapost and luatex
repositories are, and it is a subversion repo because when the project
was first added, the software system on supelec did not understand git.

The current version of Forge does support git repos, but I never switched 
since (as I wrote above) I have a small personal preference for 
subversion. So it would be possible to have a git on supelec; for that 
reason there is no need to switch to github. There may be a small
advantage to staying with supelec  as then the main project URL does not 
have to change.

OTOH, supelec's email stuff breaks easily and somewhat often.

Best wishes,
Taco

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________