Title: Re: Admin -l : anyone worked with this?
Apologies if I am on the wrong track here (I only caught the end of the thread) but assuming you are trying to deny access to all revisions of a given file not just a particular branch:
You may want to try changing the directory write permissions
Title: Re: 'Re-naming' an existing tag?
Jim Stoll Wrote:
> Section 4.7 of the CVS docs explains that the command:
>
> cvs rtag -r old_tag new_tag module_name
>
> will look for all occurences of the tag 'old_tag' in the named module and
> add a tag named 'new_tag' to the each file revision th
Title: Re: cvs export error when using commit templates
I think its a bug, however you can work around it by creating a sym link in your repository to an area that doesn't have a template defined, then create a project specifically for the purpose of exporting.
David
"Alexandru Harsanyi" <[
Title: Re: [Fwd: ignoring ID]
For various reasons (such as external vendors only releasing binaries) we use CVS to control .class files, other people may wish to store other binary files in CVS.
It may cause a problem for some people if these binary files were added to the ignore list.
Davi
(in the modules file) works, but I would still like to be able to use . as I could in CVS 1.10.5
Thanks,
David
-Original Message-
From: Garth Winter Webb [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 28, 2000 11:05 AM
To: Trott, David
Cc: '[EMAIL PROTECTED]'
Subject
Title: CVS 1.11 fails to create administrative files when using a remote repository
Apologies if this bug has already been reported, however I was not able to
find it anywhere.
I have two machines:
Machine 1 - Linux which has the repository and CVS version "1.11" (Using
pserver)
Machine 2
