[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Compared against SVN: CVS access authorization scheme
From: |
Arthur Barrett |
Subject: |
RE: Compared against SVN: CVS access authorization scheme |
Date: |
Wed, 11 Oct 2006 09:09:43 +1000 |
Reza,
You may be interested to compare CVSNT (free/GPL, runs on
unix/linux/windows/mac - just like CVS) which matches SVN feature for feature
and is generally more feature complete and oriented to commercial software
developers.
For instance CVSNT contains native:
* ACLs (including ACLs on branches)
* mergepoints (track when merges occur)
* change sets
* commit identifiers
* reserved and unreserved CM models
* Failsafe audit to MySQL, MS SQL, Postgres, SQLite, UDB/DB2
* support for the entire enterprise with Mac, Linux, Unix, Windows, OS/400 and
MVS clients
CVSNT has a very active Open Source Community as well as commercial support and
tools. CVSNT server is compatible with all CVS clients including Eclipse.
Regards,
Arthur Barrett
-----Original Message-----
From: address@hidden on behalf of Reza Mostafid
Sent: Fri 10/6/2006 9:01 PM
To: address@hidden
Cc:
Subject: Compared against SVN: CVS access authorization scheme
Hi everyone,
I am currently evaluating Subversion and CVS for use by our project.
Can somone provide info / pointers regarding the following:
Does CVS provide any means to limit or prohibit access to certain
parts of a source tree in its repository??
I know that you can do that easily in Subversion.
Regards
darbehdar
_______________________________________________
info-cvs mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/info-cvs