Hello,
* On Sun, Jan 30, 2005 at 09:47:30PM + Pierre Asselin wrote:
If you can't determine the revision or tag from which to branch, you
probably need to tighten your controls a little...
Another possiblity is to tell all your external contributors to send in
only patches, never the
On Jan 30, 2005, at 10:24 PM, [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Sander [EMAIL PROTECTED] writes:
Wait a second. The OK for addition, but wrong for commit is exactly
the status quo. The cvs add command succeeds, cvs commit fails
due to commitinfo. What
I would like to use cvs with a group of users. That fact alone is quiet
easy to handle by doing what https://ccvs.cvshome.org/fom/cache/92.html
says. The problem I have is, that the files I want to manage with cvs are
having restrictive permissions like 0700 and so on. cvs adjusts those
Thanks for the responses. I will go with the easy option of creating a separate
historical cvs area that I will put the two earlier releases into followed by
the release I started the 'live' cvs area with. That way I won't need to import
the updates that the users have made but I will still be
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
] On Behalf Of Phillips, Darren (UK)
Sent: Monday, January 31, 2005 8:24 AM
To: info-cvs@gnu.org
Subject: Re: How to use cvs with a group of users and
restrictive file perms
I would like to use cvs with a group of
Hi
Is it secure to use CVS over the Internet?.
Regards,
Néstor Boscán
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
Hello,
* On Mon, Jan 31, 2005 at 10:21:07AM -0400 Néstor Boscán wrote:
Is it secure to use CVS over the Internet?.
if you mean pserver access: There have been more than one warning not to
use that protocol over untrusted networks. That protocol was not
designed with security in mind.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Sander [EMAIL PROTECTED] writes:
On Jan 30, 2005, at 10:24 PM, [EMAIL PROTECTED] wrote:
At present, it is clear from both sides that the 'cvs add' behavior is
broken. I have probably missed some of the points, but let me try to
summarize:
Todd Denniston wrote:
assuming unix,
in proj_2_tree
|
|- dir1
|- file1 softlink to ../proj_1_tree/file1
|- dir2
|- file2 softlink to ../proj_1_tree/file2
|- file3 softlink to ../proj_1_tree/file3
|- proj_1_tree
|
|- file1
|- file2
|- file3
Is soft link the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oliver Lehmann [EMAIL PROTECTED] writes:
I would like to use cvs with a group of users.
That fact alone is quiet easy to handle by doing
what https://ccvs.cvshome.org/fom/cache/92.html
says. The problem I have is, that the files I
want to manage
Hi Mark,
If you are using a UNIX or Linux client, you
should be able to use:
umask 077
cvs checkout module
The problem is, that it isn't generious 0700 some files are having other
modes and so on... (each as restrictive as possible in that environment)
--
Oliver Lehmann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oliver Lehmann [EMAIL PROTECTED] writes:
If you are using a UNIX or Linux client, you
should be able to use:
umask 077
cvs checkout module
The problem is, that it isn't generious 0700 some files are having other
modes and so
Paul Sander [EMAIL PROTECTED] writes:
On Jan 30, 2005, at 6:40 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 28, 2005, at 8:50 AM, [EMAIL PROTECTED] wrote:
Paul Sander [EMAIL PROTECTED] writes:
On Jan 27, 2005, at 1:07 AM, [EMAIL PROTECTED] wrote:
[...]
Mark D. Baushke wrote:
Your initial problem statement seemed to indicate that this was all you
needed. If you need something else, you need to give examples of what
fails to be satisfied by this method.
Ok for example:
rwx-- file1
rwxr-x--- file2
Perhaps this is belabouring the obvious, but soft links within
repositories are not versioned, so when you want to change where the
link points to in a few months from now, you won't be able to build the
older versions of your product.
So regardless of whether you are linking to files or
Robert Lewis wrote:
I have searched thru the mail lists but can not find a
solution to the
problem. This error occurs for any operation I try to due.
Mostly I was
just trying to do a commit as a test.
cvs [commit aborted]: Invalid Lockserver version - got 1.2, wanted 2.1
I am using
Matt Doar wrote:
Perhaps this is belabouring the obvious, but soft links within
repositories are not versioned, so when you want to change where the
link points to in a few months from now, you won't be able to build the
older versions of your product.
I meant to indicate that these were
Hi,
I'm new to this list, so I start by apologizing if my question
is stupid. I did a non-robust search through the archive looking
for an answer, and came up blank, so here goes...
I have a source tree for some embedded stuff that I provide to
folks who ask for it. I had been using SourceSafe
18 matches
Mail list logo
