Dean Do wrote:
Hi,
I have a question on access control. Is there a way to prevent all commits
on the main trunk and allow commits on branches only? Once the changes on
the branch are reviewed and approved for merging into the main trunk, then
the main trunk can be manually opened up temporarily f
(gnu.cvs.help trimmed from recipient list; I can't access it)
HSP wrote:
hello, i downloaded cvs-1-11-20.zip from https://ccvs.cvshome.org but
i can´t find information about wich windows versions are supported. Is
Windows 2003 server suitable for cvs server ?
thanks in advance!!
If you're using Win
>hello, i downloaded cvs-1-11-20.zip from https://ccvs.cvshome.org but
>i can´t find information about wich windows versions are supported. Is
>Windows 2003 server suitable for cvs server ?
You may also need cygwin and other tools to run this version of CVS on Windows
Server 2003.
Alternative
Dean,
>I have a question on access control. Is there a way to prevent all commits
>on the main trunk and allow commits on branches only? Once the changes on
>the branch are reviewed and approved for merging into the main trunk, then
>the main trunk can be manually opened up temporarily for those
Dean,
>There was a very long discussion about whether it is "better"
>to perform development on the trunk or on the branch (and
>merge into Trunk) about six to twelve months ago on the CVSNT
>list. It was very good reading and I >suggest you have a read
>before making a final decision on the
The ZIP file you downloaded contains a CVS "client" suitable
for running against the Win32 API (Windows 9x, Me, NT, 2000,
XP, 2003). The CVS Project does NOT support "server" mode
on any Windows version.
Other projects do implement CVS compatible servers on Windows
but since I don't know any of t
