Hi everybody,
I'm tracking a third party software within my CVS repository. Till now, what
I've done is this:
1.- Downloaded the initial release of the 3rd party software.
2.- Create a new module within my CVS repository.
3.- Work within the HEAD main branch.
Now, another release of that 3rd
I thought that the import command together with the vendor branch was able
to cope with this problem (i.e.: just do 'cvs import your_repository
THIRD_PARTY_BRANCH a_new_release_tag' should be fine). Isn't?
Cyrille
Hi everybody,
I'm tracking a third party software within my CVS repository.
Udaya kumar.R writes:
The above mentiond setup works fine if i access the repository locally,
-d/usr/local/cvs , for both checkout and checkin. But it is not working for
the pserver method for checkin. It says 'commit requires write permission'.
You need to run pserver as root and make sure
Ripalda-Marin, Miguel-Angel writes:
I'm tracking a third party software within my CVS repository. Till now, what
I've done is this:
1.- Downloaded the initial release of the 3rd party software.
2.- Create a new module within my CVS repository.
3.- Work within the HEAD main branch.
Now,
On Mon, 14 Oct 2002, Ripalda-Marin, Miguel-Angel wrote:
Hi everybody,
I'm tracking a third party software within my CVS repository. Till now, what
My condolences. ;)
I've done is this:
1.- Downloaded the initial release of the 3rd party software.
2.- Create a new module within my CVS
Mark Cooper writes:
Obviously this depends on the relative number of files in the 3rd party
software release that have changed since the last one, but I too manage 3rd
party software via cvs and have (unless the 3rd party software release has
a completely different folder/directory
At 01:49 PM 10/14/2002, Anne McCaffrey wrote:
To implement additional security, I have made all
Attic directories in the repository read only
...
but today when a developer tried to
add a new file,cvs add was aborted with the
error,Cannot read Attic directory.Permission denied.
Only when I gave
--- Anne McCaffrey [EMAIL PROTECTED] wrote:
Hi all,
I am facing problems with Attic directories.
I have a script that disallows users from removing
files using cvs remove.
To implement additional security, I have made all
Attic directories in the repository read only, since
all users
On Tue, 2002-10-15 at 03:14, Kaz Kylheku wrote:
The problem with the vendor branch is that it starts at version 1.1 of every
file (1.1.1.1 really, but that's an internal detail). You cannot start
a vendor branch somewhere halfway up your trunk, so vendor branching is
useless for the case
Hi
No,the files are not added to branch.
The 'Branch' is MAIN and the CVS tags shows HEAD.
It is the requirement of our project that no single
developer should remove files(even using cvs remove)
without consulting others involved and the PM; some of
them have removed files previously which
[ On Monday, October 14, 2002 at 11:52:12 (-0700), Anne McCaffrey wrote: ]
Subject: Re: Problems with Attic permissions
It is the requirement of our project that no single
developer should remove files(even using cvs remove)
without consulting others involved and the PM; some of
them have
Hi
I understand that you may feel this is 'silly' but
that really is beside the point.My original question
was something else, if you noticed.
Regards,
Anne
--- Greg A. Woods [EMAIL PROTECTED] wrote:
[ On Monday, October 14, 2002 at 11:52:12 (-0700),
Anne McCaffrey wrote: ]
Subject: Re:
Hi,
After reviewing the documentation, I'm a bit confused as to whether or not an alias
module can contain multiple aliases or directories in some sort of delimited list.
Consider the following two examples:
(1) Alias module definition:
admin
On Mon, 14 Oct 2002, Anne McCaffrey wrote:
That's kinda silly. Any file which has
``accidentally'' been removed
with cvs rm can trivially be resurrected with cvs
add and the
resulting history will show clearly who the guilty
party is.
Why use a sledge hammer when a tack hammer
--- Kaz Kylheku [EMAIL PROTECTED] wrote:
On Mon, 14 Oct 2002, Anne McCaffrey wrote:
That's kinda silly. Any file which has
``accidentally'' been removed
with cvs rm can trivially be resurrected with
cvs
add and the
resulting history will show clearly who the
guilty
party is.
[ On Monday, October 14, 2002 at 14:04:33 (-0700), Anne McCaffrey wrote: ]
Subject: Re: Problems with Attic permissions
I understand that you may feel this is 'silly' but
that really is beside the point.My original question
was something else, if you noticed.
You wouldn't have your original
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
An update on the problemthis happens on the command line as well as in
the script.
'cvs -Qn rdiff -r 1.1 -r 1.2 -u module/file' fails with:
cvs [rdiff aborted]: cannot open /tmp/cvsyE7DIO: File exists
Using: CVS 1.11 (client/server)
Thanks!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ok, I've narrowed it down even moreit fails if I add the '-n' option.
'cvs -Q rdiff -r 1.1 -r 1.2 -u module/file' works. Any ideas on this?
Thanks!
~Paul
On Monday 14 October 2002 10:02 pm, Paul Nicholson wrote:
Hey,
An update on the
18 matches
Mail list logo