-Original Message-
From: Frederic Brehm <[EMAIL PROTECTED]>
Sent: Feb 18, 2004 5:27 PM
To: [EMAIL PROTECTED]
Subject: Re: how to support symlinks?
At 04:58 PM 2/18/2004, Eric Siegerman wrote:
>a simple mechanism has been implemented
Perhaps it is really, really simple:
cat .sy
On Wed, 18 Feb 2004, Larry Jones wrote:
> Robert P. J. Day writes:
> >
> > does anyone have a copy of this, or whatever people have settled on as
> > a common solution?
>
> Since my previous response was apparently not clear enough, the common
> solution is to create the symlinks as an integra
I just read to the NEWS for cvs 1.11.13 - can this check for the broken pipe
signal.
Regards
Gurpreet S
-Original Message-
From: Gurpreet Singh (SCM) [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 19, 2004 10:23 AM
To: '[EMAIL PROTECTED]'
Subject: error faced...frequently on a file
Hi,
this is a newby question.
I am using CVS with the TortoiseCVS client. This client opens files always
with the
cvs edit -c
command, which makes sense in my case, because I am working only with binary
files and concurrent editing would lead to unsolvable conflicts.
The problem is that, when the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Viraj Purang wrote:
>Everytime I try to "cvs update" a file called ".buildnum"
>
>I get an error :
>"cannot rename file .new..buildnum to .buildnum"
>
>This is true for all files which have been changed on client workspace
>and are thus different from
> [ On Wednesday, February 18, 2004 at 10:21:41 (-0500), Jim.Hyslop wrote: ]
> > Subject: RE: Binary release announcements?
> >
> If you can't, or won't, build the software you use yourself then you
> need to find someone who can _and_ who you trust to do that for you.
>
Some people seem to be awfu
edit -c (regrettably in my opinion) is not a part of the official version of
CVS which is the subject of this mailing list. There is a patch available
(see http://mail.gnu.org/archive/html/info-cvs/2003-12/msg00135.html)
which gives you cvs edit -c in the "standard" cvs, but it is more likely you
a
mark francisco wrote:
Hi Yanglong,
Now here is the address for my user-friendly CVS quick start howto
(forum). https://125.15.160.110/bzoffice1/. I set this forum just for
Sorry guys. The address is https://129.15.160.110/bzoffice1/.
this dear CVS issue since I have tried for a long ti
We now have developers working in multiple branches.
When ready I merged their branches into a release branch.
When merging I'm finding myself fixing the same conflicts over and
over.
I have a feeling I'm missing something simple in our process. Any enlightenment?
Chances are you're using the default common ancestor for each merge. The
3-way merge algorithm then rediscovers each change made cumulatively on both
branches each time. The solution is to specify the result of the last merge
as the common ancestor when you run "cvs update". For that, you must t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Gelderblom (ptok) wrote:
>edit -c (regrettably in my opinion) is not a part of the official
version of
>CVS which is the subject of this mailing list. There is a patch available
It is the longstanding policy of this team that changes to the sou
I need to access CVS via SSH. I would like to have several different product modules
with different users having different access rights to each one.
For example, I have projects 1-5 and users 1-5 and I would like to have access
something like
Project 1
users 1, 2, 3, 4 & 5
Project 2
12 matches
Mail list logo