Yes there is: Do not ever modify the CVS controlled file!
Always, and only ever, modify a copy of any file if you don't want CVS
to see your changes to it!
I.e. this is a build system problem, not a CVS problem.
No, it's not a CVS problem.
However, CVS could make life easier with this as an
I've got a file which I must make changes to on my system. However, I
don't ever want my changes put back into the repository.
Currently, I handle this by removing the file and re-updating the file
from the repository before doing a commit.
But is there a way I can tell CVS - always update
Apologies if this has been done before, but I can't find it
anywhere. I want to process some binary files on a mac running
OSX, using the command line CVS that comes with BSD,
instead of using the GUI version. specifying a -kb on the
command line treats the files as binary, but I'm not
On Tuesday, May 14, 2002, at 10:54 AM, Joi Ellis wrote:
This is a problem when one wants to edit on windows but actually build
and execute the app on unix. The obvious way of getting the files
back into the unix environment is to commit them to the repository and
then run cvs update on the
In using a cvs server located on Unix, we've run into problems because
/tmp is full.
We're trying to redirect the temporary files until we can add some more
space to /tmp.
1) Am I correct in that passing the -T parameter (or setting TMPDIR)
from the client with a absolute path to the
In using a cvs server located on Unix, we've run into problems because
/tmp is full.
We're trying to redirect the temporary files until we can add some more
space to /tmp.
1) Am I correct in that passing the -T parameter (or setting TMPDIR)
from the client with a absolute path to the
On Thursday, February 7, 2002, at 11:24 PM, E B wrote:
Probably you guys havent read my mail clearly.
How does a client have access to the modules files
on the server? Is there any cvs admin command that
will do this?
You checkout CVSROOT/modules, make your changes and then commit it.
I'm no CVS expert, but in my thinking, the easiest thing to do would be
to merge the branch into the trunk at the last point before the files
where renamed. Then rename the files and split off a new branch.
If you've already renamed the files on the trunk, I'd still do the same
thing:
1)
I'm no CVS expert, but in my thinking, the easiest thing to do would be
to merge the branch into the trunk at the last point before the files
where renamed. Then rename the files and split off a new branch.
If you've already renamed the files on the trunk, I'd still do the same
thing:
1)
Myself and another programmer are working on a project. We're working
mainly on different sections of the code.
Day 1: I checkout the project
Day 2: I make changes and commit them, and then continue working on my
working copy.
Day 3: Programmer B makes changes and commits them
Day 4: I
10 matches
Mail list logo
