Re GIT on Windows my remark was just quoting 
http://www.infoq.com/articles/dvcs-guide

where it says under GIT
      Poor Windows support

I guess we could take a vote of all developers (weighted by
activity....:-)

What I am not seeing is either
a) a clear statement of the advantage of DVCS over VCS
b) a true comparison between the contenders

I am not sure that speed or web interfaces are high in my criteria.
Simple, non breaking commandline with checkable history is near the
top.  Ease of set up; lack of breaking modes....
==John ffitch

------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

http://www.youtube.com/watch?v=4XpnKHJAok8

-----Original Message-----
From: john ffitch [mailto:jpff@codemist.co.uk] 
Sent: Friday, February 04, 2011 10:32 AM
To: csound-devel@lists.sourceforge.net
Subject: [Cs-dev] DVCS

Re GIT on Windows my remark was just quoting 
http://www.infoq.com/articles/dvcs-guide

where it says under GIT
      Poor Windows support

I guess we could take a vote of all developers (weighted by
activity....:-)

What I am not seeing is either
a) a clear statement of the advantage of DVCS over VCS
b) a true comparison between the contenders

I am not sure that speed or web interfaces are high in my criteria.
Simple, non breaking commandline with checkable history is near the
top.  Ease of set up; lack of breaking modes....
==John ffitch

----------------------------------------------------------------------------
--
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Fri, Feb 4, 2011 at 13:32, john ffitch  wrote:
> Re GIT on Windows my remark was just quoting
> http://www.infoq.com/articles/dvcs-guide
>
> where it says under GIT
>      Poor Windows support
>
> I guess we could take a vote of all developers (weighted by
> activity....:-)

My activity is pretty low so I've avoided commenting, but, since we
are going to weight  votes I might as well talk :p.

>
> What I am not seeing is either
> a) a clear statement of the advantage of DVCS over VCS

1. Being able to work offline, and still commit in sensible chunks
(ie: one change, one commit).
2. Being able to work, and then beautify the commit log/history before
pushing (eg, work on something, test, fix up a bug in the new feature,
and squash them into a single commit before pushing).
3. This is not an advantage of the DVCS model, but all DVCS have
better branch/merge support than centralized VCS.
4. Private branches for experimentation.
5. Entire commit history is available on every checkout, therefore
things like bisecting or annotating become easier to do.

Advantages over CVS in particular:

1. Atomic commits
2. File copying/moving/renaming history is preserved.

> b) a true comparison between the contenders

I can't really answer this one. Wikipedia has a comparison [1], the
features tables may be useful.

>
> I am not sure that speed or web interfaces are high in my criteria.
> Simple, non breaking commandline with checkable history is near the
> top.  Ease of set up; lack of breaking modes....

I have previously converted a csound repository into git, it takes a
while but it works (just rsync the csound cvs repository [the server
thing, not a checkout], and run git cvsimport on that), no history
that I could discern was lost.
USer interface can be read about here[2] for SVN users, but SVN
interface is practically the same as CVS, so it should work here as
well.


[1] http://en.wikipedia.org/wiki/Comparison_of_revision_control_software
[2] http://git.or.cz/course/svn.html
-- 

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://li