Hi All,
Using i.e cvs update -j revision 1.6 -j revision 1.3 file.c, we discard
changes from 1.6 to 1.3. Then, commiting, we get revision 1.7 that is exactly the same
as 1.3. Now, suppose I want to generate a new revision of file.c but containing code
from 1.1 to 1.3 + 1.5 and
Hi.
I am a CVS newbie and I would like to do/have the following:
There is a Server with an CVS Repository sv in the path /var/lib/cvs/sv.
On the clients I work with:
CVSROOT=:ext:[EMAIL PROTECTED]:/var/lib/cvs;
LOCAL=/SOMEWHERE/sv;
CVS checkout is done by:
cd /SOMEWHERE;
cvs
K. Posern [EMAIL PROTECTED] writes:
But I need an exact copy of the version a CLIENT has in its
/SOMEWHERE/sv dir on the SERVER (so without the rcs stuff).
How can I achieve this? Do I have to to do an cvs-checkout on the
server and cvs-update everytime a client did commit something?
Or
Hi.
I am a CVS newbie and I would like to do/have the following:
On the clients I work with:
CVSROOT=:ext:[EMAIL PROTECTED]:/var/lib/cvs;
LOCAL=/SOMEWHERE/sv;
CVS update is done by:
cd /SOMEWHERE/sv;
cvs -d $CVSROOT update -dP;
CVS commit is done by:
cd
Hello,
* On Thu, Aug 26, 2004 at 12:20:14PM +0200 K. Posern wrote:
But I need an exact copy of the version a CLIENT has in its
/SOMEWHERE/sv dir on the SERVER (so without the rcs stuff).
Have a look at C.3.5.2 of your manual:
Title: Question about process scheduleing
I'm trying to look into a problem with the amount of time it takes us to do a checkout of a large (800 meg) module.
On most of the machine in the shop it takes between 10 and 15 minutes, on one machine it can take an hour.
When I look at top on
K. Posern wrote:
But I need an exact copy of the version a CLIENT has in its
/SOMEWHERE/sv dir on the SERVER (so without the rcs stuff).
How can I achieve this? Do I have to to do an cvs-checkout
on the server and cvs-update everytime a client did commit
something?
Or can I say to the server
[EMAIL PROTECTED] writes [in very long lines]:
Using i.e cvs update -j revision 1.6 -j revision 1.3
file.c, we discard changes from 1.6 to 1.3. Then, commiting, we get
revision 1.7 that is exactly the same as 1.3. Now, suppose I want to
generate a new revision of file.c but containing
Hello all,
The latest version of CVS, version 1.12.n (n5), changed the format of
its output on commit messages. This unfortunately breaks pcl-cvs mode
in emacs, which uses the commit messages to determine which files have
been committed. It is of course possible to alter pcl-cvs to parse
the new
Lynch, Harold wrote:
I'm trying to look into a problem with the amount of time it takes us to
do a checkout of a large (800 meg) module.
On most of the machine in the shop it takes between 10 and 15 minutes,
on one machine it can take an hour.
When I look at top on the cvs server, the process
Lynch, Harold wrote:
I'm trying to look into a problem with the amount of time it takes us to do
a checkout of a large (800 meg) module.
On most of the machine in the shop it takes between 10 and 15 minutes, on
one machine it can take an hour.
When I look at top on the cvs server, the
Lynch, Harold writes:
On most of the machine in the shop it takes between 10 and 15 minutes,
on one machine it can take an hour.
Look for network problems with that machine -- that sounds like dropped
packets and retransmissions.
-Larry Jones
Yep, we'd probably be dead by now if it wasn't
One problem I regularly face is: how to build two different versions of
a project which differ in only a very small subset of files. One of
these versions is obviously the trunk version. It would be extremely
convenient if this could be achieved by simply
cvs co (or update) -A myproject
cvs
13 matches
Mail list logo
