-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Terrence Enger [EMAIL PROTECTED] writes:
Greetings,
I have the feeling that I may have seen the answer to this
question here lately, but I cannot find it now. Please
accept my apologies if this is a repeat.
What is the method for read
Hi Tyler,
On Fri, 18 Jun 2004, Tyler wrote:
How do I safely move the files from branch A to branch B?
For a small change like this, it's easiest to:
- back out the changes from branch A
(in A sandbox)
cvs up -j[new rev] -j[previous rev] [list of files]
(verify changes and commit)
-
Hello,
I am moving from cvs 1.12.2 to 1.12.9, and in order to have my taginfo
scripts working, I had to use
%t %o %r/%p %{sv}
as the taginfo line format string, instead of the default
%t %o %p %{sv}
in order to have me old taginfo scripts working as before.
This makes me suspect that
Could we lose information if we delete a user from CVS
The information transmitted is intended only for the person or entity to whom it is addressed and may contain confidential and / or privileged Material. Any review, re-transmission, dissemination or other use of or taking of
Hello,
I've added checkoutinfo to cvs-1.12.9, slightly based on a patch from
Andrey Aristarkhov that found in the mailinglist archive (but can't seem
to find again).
I use it to have more detailed control over who can checkout and commit
to specific repositories, directories and branches, in
On Jun 20, 2004, at 5:06 PM, Adrian Constantin wrote:
Does anyone has an ideea as how can I have the
public directory kept clean, that is without the CVS
subdirectory ? Can I move the CVS subdirectroy out
of the sandbox ? I would need something like
'cvs release' but that would actually
Hello,
I'm replying to an old mail (and answer) from me, because I took the
time to generate a skript which shows the behaviour I mentioned (and it
still happens, even with 1.11.17).
My first posting on this can be found on
http://lists.gnu.org/archive/html/info-cvs/2004-04/msg00201.html
My
Information ? are you talking about the revision
history linked to that user.
No it
should not effect the file revision history attached to that ''deleted'' user.
Regards, Gurpreet S
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of
Hi,
can we anyhow restrict CVS access based on IP.
Say like want to deny certain IP's to being connected to the CVS server
(Linux sandbox).
Regards,
Gurpreet S
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Geoff
Beier
Sent: Monday, June 21, 2004 6:39
can we anyhow restrict CVS access based on IP.
Say like want to deny certain IP's to being connected to the CVS server
(Linux sandbox).
This question doesn't really have anything to do with the message you
included, AFAICT...
The best way to do this is to use features built in to your OS. For
Ok what's the proper way of putting scripts into this
directory that the cvs files can use. For example I want
to call a buglog.sh file from the loginfo file. Do I
- checkout the $CVSROOT/CVSROOT directory
- cvs add buglog.sh file
- modify loginfo to call the buglog.sh file
- cvs commit
- cp
If you use the cvspserver descripted by /etc/xinet.d/cvspserver you can use
the tcpwrappers of xinetd (file /etc/hosts.allow and /etc/hosts.deny) :
in the file /etc/hosts.allow, add the line
ALL : 127.0.0.1
cvs : 192.168.0.3 192.168.0.1 (here the ip adresses or subnet you want to
allow)
in the
On Jun 21, 2004, at 1:54 PM, [EMAIL PROTECTED] wrote:
Ok what's the proper way of putting scripts into this
directory that the cvs files can use. For example I want
to call a buglog.sh file from the loginfo file. Do I
- checkout the $CVSROOT/CVSROOT directory
- cvs add buglog.sh file
- modify
[EMAIL PROTECTED] writes:
Ok what's the proper way of putting scripts into this
directory that the cvs files can use.
As usual, the answer begins with That depends If you don't care
about revision control on the scripts, then you can just copy them into
the directory. If you do want
At 02:07 PM 6/21/2004, Larry Jones wrote:
If you don't care
about revision control on the scripts
Horrors! Heretic!
:-)
Fred
___
Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/
Hello all,
I'm new to CVS and I would like to make a CVS server (with cvs-1.11.15) on a
Redhat 7.3 station and access this server with a WinCVS 1.3.13 client on a
WinXP station. I am using the gserver access method.
On the server, I configured the server as it is described in
- Ensure correct rwx permissions for ../CVSROOT/buglog.sh
A good idea, but it shouldn't be necessary if you set them
correctly before checking it in the first time. If you
neglected to do that, you can set the permissions on the RCS
file and CVS should copy them to the checkout out file in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
- Ensure correct rwx permissions for ../CVSROOT/buglog.sh
A good idea, but it shouldn't be necessary if you set them
correctly before checking it in the first time. If you
neglected to do that, you can set the
[EMAIL PROTECTED] writes [quoting me]:
If you
neglected to do that, you can set the permissions on the RCS
file and CVS should copy them to the checkout out file in the future.
Sorry I missed this. Where in the RCS files? I see access; so I'm
assuming it's there, but set to what?
Not
Yes thanks you. A couple of folks have pointed that out
already and I did a Duhhh response. So I did this and
it worked, but it worked too good. I set the perms.
on the RCS file to r-xr-x---, but when I checked out/
checked in/commit, RCS file had r-xr-xr-- (gave read
permission to others). Why?
20 matches
Mail list logo
