we handled this by forcing versions on the branches when we create
them with the "cvs ci -F" command then we wrote a reserve script that
gets the revision from the CVS/Entries file and locks it "admin -
l$rev"
--- In [EMAIL PROTECTED], Joerg Faschingbauer [EMAIL PROTECTED] wrote:
"Rich" ==
Cristian Gheorghe wrote:
Original Message
Subject: Strange error msg when using 'export' in CVS
Date: Thu, 04 Jan 2001 19:48:52 GMT
From: Cristian Gheorghe [EMAIL PROTECTED]
Organization: Deja.com
To: [EMAIL PROTECTED]
Hello,
I need some help with the 'export'
Michael Peck writes:
I also discovered that as the history file (CVSROOT/history) grows, it
really becomes a HUGE bottleneck.
If you delete/rename the file, cvs will stop appending to it.
As of CVS 1.11, you can also set LogHistory in CVSROOT/config to only
record events that you're
Cristian Gheorghe writes:
cvs [export aborted]: can not write CVS/Template file: No such file or
directory
This is a CVS bug that is already fixed in the current development
version (see www.cvshome.org for details of how to get the current
development version if you're interested).
For permissions maintainability reasons, it'd be great if you could also specify
the location of CVSROOT files that need to be writable by everyone.
Noel
[EMAIL PROTECTED] on 2001.01.05 11:58:12
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED], [EMAIL PROTECTED] (bcc: Noel L Yap)
Subject:
I have found that it is ok to symlink *directories* in the CVS repository,
but you should not symlink individual files. CVS uses locks on a
per-directory basis to handle concurrency, and linking a file across
directories allows multiple cvs processes to access the file simultaneously
and
Hope this post isn't out of line with the purpose of this group but I
don't know where else to turn...
We're looking for a CVS consultant/guru that can help us with CVS
needs assessment, architecture, deployment, training and on-golng
support. We're located South of Market in SF.
Please feel
Eric has some good ideas. I wonder if we could get Paul Eggert to add
support to RCS to directly fetch and set newphrases, in case someone needs
them someday.
However:
--- Forwarded mail from [EMAIL PROTECTED]
- One can imagine adding a per-revision attribute that says
where in the
Why can't you place the header files in their own module, and include
that module in another one, using either the -a or operators?
Another method that's used successfully is to create baselines to which
developers create references. Your symlink method is one way to do it,
but there are
Hi
One of the developers in our project reported a
problem.He commited a file after fixing a bug as
revision number 1.115.Later some one commited another
revision of the same file(1.116).Now the first
developer updated his copy from the rep and ran the
program and noticed the same bug and after
I am *very* new to CVS and have a user that wishes to emulate a behaviour
similar to commitinfo. What he wants is this:
He has a perl script under cvs control, and it depends on other files
under cvs control in other projects. Is there a way to have those other
files updated when he
Paddy T writes:
One of the developers in our project reported a
problem.He commited a file after fixing a bug as
revision number 1.115.Later some one commited another
revision of the same file(1.116).Now the first
developer updated his copy from the rep and ran the
program and noticed the
On Fri, Jan 05, 2001 at 01:48:32AM +, Kenn Humborg wrote:
Starting with an empty CVS tree, we did
cvs import -b 2.2.14 module vendor vendor-2-2
[...]
We continued development, adding files and modifying a few
vendor files.
Now I'm trying to import an updated vendor tree [...]:
Title: Untitled Document
info-cvs´Ô ¾È³çÇϼ¼¿ä? gnu.org¿¡¼ info-cvs´ÔÀÇ ¾ÆÀ̵𸦠º¸°í ½Å³âÀλç
µå¸³´Ï´Ù. »õÇØ¿¡ ±â¿øÇϽô ¸ðµçÀÏÀÌ·ç¾î Áö½Ã±æ ¹Ù·Î°í¿ä. ½¬´Â½Ã°£,¿Ü·Î¿ï¶§ "½ß¼î"°¡ ÇÔ²²ÇÔÀ» ÀØÁö ¸»¾ÆÁÖ¼¼¿ä. ^^
Most likely what happened was this:
- Users A and B updated to version 1.114.
- User A modified and committed the file, creating version 1.115.
- User B modified the file, but his commit was blocked.
- User B did a "cvs update".
- User B decided not to complete the merge, and renamed his backup
On Fri, Jan 05, 2001 at 04:12:23PM -0500, Eric Siegerman wrote:
I've scrambled enough repositories that I've come to think of
importing as a dangerous operation -- dangerous enough to be
worth backing up the repository first. (Not that I'm scrupulous
about actually doing this, alas; there've
On Sat, Jan 06, 2001 at 12:01:49AM +, Kenn Humborg wrote:
On Fri, Jan 05, 2001 at 04:12:23PM -0500, Eric Siegerman wrote:
I've scrambled enough repositories that I've come to think of
importing as a dangerous operation
Unfortunately, I was still under the impression that pretty much
I encounter a problem when using WinCVS1.16b.
Firstly I creat a cvsroot in Linux,and import a directory named "target" with
version 1.1.1.1. Then change files in target and commit them with version 1.2,1.3.
A day,I casually again import a directory named "target" to
18 matches
Mail list logo
