Hi Rod,
If you don't need file merging, then I suggest creating a script which is
stored in the customisations, which automatically checks out the required
version and performs the xcopy across. We do a similar thing in our
release script for our software -- it checks out the version to release,
Hi Folks,
The good part is, we are getting some of this old code installed into CVS
repositories.
The bad part is, we are getting some of this old code installed into CVS
repositories. This means we need a CVS client that will run under Windows
for Workgroups 3.1. I moderate search did not find
first, thanks everyone who answered my question.
second, this works like a charm. and i learned a WHOLE LOT in the
process.
On Tue 07 Oct 03, 9:38 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] said:
On Tue, 7 Oct 2003 [EMAIL PROTECTED] wrote:
hi all,
i've read about remote cvs
Maybe a DOS client would work.
http://www.cvshome.org/dev/codezother.html
On Wednesday 08 October 2003 01:33 pm, Schrum, Allan (Allan) wrote:
Hi Folks,
The good part is, we are getting some of this old code installed into CVS
repositories.
The bad part is, we are getting some of this old
On Wed, Oct 08, 2003 at 10:59:37AM -0700, [EMAIL PROTECTED] wrote:
this ssh method requires that my co-developer has an account on the
system containing the repository. i don't mind that, since he's a
friend.
but in general, someone who accesses cvs this way has system access.
not only can
On Wed, Oct 08, 2003 at 10:59:37AM -0700, [EMAIL PROTECTED] wrote:
but in general, someone who accesses cvs [via SSH] has system access.
not only can my co-developer do things like cvs checkout and cvs
commit, but he can also ssh into the machine and work at a remote
shell.
is there a way
Here's an odd one:
One of our developers is having difficulties committing five of his
files. The problem files are all in the same directory. Here are the
facts:
* The files in question are text files, Java source code.
* The clients in question are JBuilder 7, Tortoise CVS 1.4.5, and
WinCvs
On Wed, Oct 08, 2003 at 12:14:17PM -0700, Kyle Adams wrote:
Anyone have any idea where the problem might be?
Not a clue :-(
But here are some things you can try to get more info:
- run the client with (global) -t to get a debugging trace
- define the CVS_CLIENT_LOG environment variable, to
