--- Pierre Asselin <[EMAIL PROTECTED]> wrote:
> "vincent_choplin" <[EMAIL PROTECTED]> writes:
> >would we have to stop working while we put CVS up
> or can one of us do
> >it while the others go on with the developpement?
>
> Nah, don't stop. When CVS is ready, import what you
> have and save
>
"vincent_choplin" <[EMAIL PROTECTED]> writes:
>I work in a small but still growing company and we're beginning to
>need something like CVS...
>[...] Is it worth hiring a temp. or consultant to install and
>teach us?
A consultant may be a good idea in such circumstances. The trick is
to find
It's a piece of cake to install CVS server on Unix. I
haven't had experience doing so on NT (you'll probably
need the Cygwin port).
In addition to getting past initial problems, a
consultant would also get you up and running with the
CVS way of doing things (in my experience, each
version contro
This is kind of a "how long is a piece of string" question.
I would feel comfortable reccomending Linux over NT simply because I
have used Linux as a CVS server in a heterogeneous environment (Win*,
Mac*, Solaris and Linux) and it has worked like a charm.
As to the cost, it depends ...
As to
ECTED]]
Sent: 11 January 2002 10:08
To: [EMAIL PROTECTED]
Subject: cost of CVS...
I everyone.
I work in a small but still growing company and we're beginning to
need something like CVS...
the problem is that nobody here has ever used CVS (nor any of its
pairs) and one person only (me) i
I everyone.
I work in a small but still growing company and we're beginning to
need something like CVS...
the problem is that nobody here has ever used CVS (nor any of its
pairs) and one person only (me) is familiar with VSS, on user side
only.
I would really appreciate you giving me an appr