On Sat, Oct 04, 2003, Mark D. Baushke wrote:
> Ralf S. Engelschall <[EMAIL PROTECTED]> writes:
>
> > The patch adds two still missing and very important auditing hook
> > facilities to CVS: "CVSROOT/importinfo" for auditing "cvs import"
> > op
ceed to the
next possible contributions derived from my OpenPKG CVS patch set.
Yours,
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
This patch adds two still missing and v
s (for easier review by the
CVS developer team).
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
___
Info-cvs mailing list
OpenPKG package for CVS:
http://cvs.openpkg.org/openpkg-src/cvs/cvs.patch.rse
Controlling "cvs add" is currently not supported, but this usually isn't
a big deal. I just run a little cronjob once per day to remove empty
dirs from our CVS repositories..
cvstrac.org/) does.
There you also can identify a commit as a whole. If you need immediate
action, use the first attempt. If it is ok to update your database in
time intervals, use the second attempt.
Ralf S. Engelschall
erations are update
and difference operations in my experience. So I recommend you to focus
more on a read-only backup repository -- which in especially trivial to
setup.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
lly separate CVS repository.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
ow to use those hooks, please.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
___
Info-cvs mailing list
[EMAIL PROTEC
gram and hook it in into commitinfo.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
PTH_1_3_4: 1.488.2.6
This is with CVS 1.11.5.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
___
Info-cvs mailing
On Sun, Feb 09, 2003, Reinstein, Shlomo wrote:
> Suppose I would like to find out which tags a module has, _without_ first
> checking it out. Can this be done? If so, how?
You can run "cvs rlog" before "cvs checkout" to see the existing tags.
e settings on a
by-host basis in your ~/.ssh/config (e.g. "ForwardX11 no").
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
s" files in the "Setup" dialog. CVSTrac then operates in a full
read-only and non-destructive way.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
___
penpkg.org/openpkg-src/cvs/cvs.patches.rse) and
use the "importinfo" hook it provides for this. That's what OSSP shiela
(see http://www.ossp.org/pkg/tool/shiela/) successfully uses for access
controlling the "cvs import" operations on the CVS repositories of
OpenSSL, OSSP and Ope
sure that your server load does not increase, you
should also have a look at CVSTrac (http://www.cvstrac.org/). It is a
lot faster and provides some nice features like a Timeline, etc.
Ralf S. Engelschall
repository, can use tagging utility. Now we want to restrict some users to
> do tagging.
See the CVS manual for the "taginfo" hook.
Ralf S. Engelschall
[EMAIL PROTECTED]
Be careful, OSSP shiela and similar tools do _NOT_ restrict your users
from _EDITING_ the same file at a time. As explained above, this is
against the design of CVS. OSSP shiela and similar tools "just" restrict
the _COMMIT_ access to files.
have checkout/read/write/commit
> access to Xdoc, Ydoc, Zdoc, but no access at all to X, Y, Z.
>
> (I'm cvs admin; I'd like to do anything to any project)
Have a look at OSSP shiela (http://www.ossp.org/pkg/tool/shiela/). It
can provide you flexible access control to modules base
1.34+3 -3 openpkg-src/amd/amd.spec
| 1.3063 +1 -0 openpkg-web/news.txt
In your case you perhaps just want the header, the log and the summary
parts from above.
Ralf S. Engelschall
inally implemented this two years ago for use with the ASF's
Apache CVS repository and my Laptop and using it since this time on a
daily basis with the OpenSSL, OpenPKG and OSSP projects. The nice thing
is that you do not have to change the ways you are used to work with CVS
and still get the a
others, too. Feel free to rip out whatever you like, the patches are
not copyrighted or otherwise restricted.
You can find the latest patchset in the OpenPKG CVS repository:
http://cvs.openpkg.org/openpkg-src/cvs/cvs.patches.rse
So see them in action, you can apply them yourself to a vanilla
CVS 1.11
http://cvs.ossp.org/pkg/tool/shiela/
Distribution ... ftp://ftp.ossp.org/pkg/tool/shiela/
Ralf S. Engelschall
[EMAIL PROTECTED]
___
Info-cvs mailing list
[EMAIL PROTECTED]
eady fiddled around with CVS'
>internals here. But I still was unable to force CVS to always pick up all
>files. So, which piece of code has to be patched?
>
> Please sched some light on this problem. Thanks.
Still nobody who can help with this? I would apprecia
In article <[EMAIL PROTECTED]> you wrote:
> Ralf S. Engelschall writes:
>>
>> 1. The repository was copied from the remote site to the local site
>> 2. The working directory was checked out from the local site
>> 3. Some files in the top-level of the workin
ease don't say "just
look in commit.c and recurse.c". I've already fiddled around with CVS'
internals here. But I still was unable to force CVS to always pick up all
files. So, which piece of code has to be patched?
Please sched some light on this problem.
tutions?
They are using a patched CVS version which supports this additional
keyword.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
26 matches
Mail list logo
