Hello,
I had the problem you discribe by myself.
According to my findings there are at least three possibilities:
a) a script in CVS distribution (/usr/local/cvs-1.11.6/contrib):
cvs_aclsA perl script that implements Access Control Lists
by using the
Hi,
I'm experimenting a little with the log command, and I found a strange
behaviour.
When using cvs log -rHEAD, I successfully get the log messages for the
trunk.
But wit cvs log -rHEAD., (with a dot) which should give me the log message
for the last revisions on the trunk, I just get:
cvs
Julien Wajsberg writes:
When using cvs log -rHEAD, I successfully get the log messages for the
trunk.
No, you don't. HEAD is the most recent revision on the *default*
branch, which need not be the trunk; it could be a vendor branch. And
you should only get the log message for the most
All;
We seem to have two different styles to working with CVS here and I wantto
know what the standard is in the community.
One group says that you never ever change your working area. You just do updates
and keep working on. The other group says you should change your working
area and
On Mon, 2003-09-22 at 12:42, [EMAIL PROTECTED] wrote:
All;
We seem to have two different styles to working with CVS here and
I want to know what the standard is in the community.
One group says that you never ever change your working area. You
just do updates and keep working on.
On Mon, Sep 22, 2003 at 02:37:08PM -0400, Tom Copeland wrote:
On Mon, 2003-09-22 at 12:42, [EMAIL PROTECTED] wrote:
All;
We seem to have two different styles to working with CVS here and
I want to know what the standard is in the community.
One group says that you never ever
On Mon, Sep 22, 2003 at 02:37:08PM -0400, Tom Copeland wrote:
On Mon, 2003-09-22 at 12:42, [EMAIL PROTECTED] wrote:
All;
We seem to have two different styles to working with CVS here and
I want to know what the standard is in the community.
One group says that you never ever
We are running a client/server configuration using SSH. The server in running
Linux and cvs 1.11.6 and clients are using mainly CVSNT.
In order to refactor the build we need to limit the access to the build.xml
file to a limited group. I have looked through the documentation, but still not
sure
Larry Lords writes:
In order to refactor the build we need to limit the access to the build.xml
file to a limited group. I have looked through the documentation, but still not
sure what to do to limit the access?
CVS cannot limit access to a single file, only to a directory.
-Larry Jones
On Tue, 23 Sep 2003 07:16 am, Larry Jones wrote:
Larry Lords writes:
In order to refactor the build we need to limit the access to the
build.xml file to a limited group. I have looked through the
documentation, but still not sure what to do to limit the access?
CVS cannot limit access to
10 matches
Mail list logo
