Hi Folks,
Gerhard Sittig <[EMAIL PROTECTED]> wrote:
>There's a file /usr/src/contrib/cvs/FREEBSD-upgrade (if only I
>had the bookmark around with the web frontend to the FreeBSD
>source repo -- I can provide it on Tuesday) with the most
>important section for you at its end:
If you are interested in looking directly at the cvs repository used
by FreeBSD, you should be able to checkout a copy of it for yourself:
cvs -d :pserver:[EMAIL PROTECTED]:/home/ncvs login
CVS password: anoncvs
cvs -d :pserver:[EMAIL PROTECTED]:/home/ncvs co contrib_cvs
or just browse it through the web via
http://www.FreeBSD.org/cgi/cvsweb.cgi/src/contrib/cvs/
to take a look at it.
There look to be some cool patches to cvs in the FreeBSD sources and
some that I probably want to think a bit about first. A brief look at
the diffs turns up the following changes (this may not be an
exhaustive list -- [EMAIL PROTECTED] may be able to give you a better
list):
+ a -R switch that allows a read-only repository (CD-ROM) to be used
(no lock files are created).
+ a -g switch to play with group-write permissions on working files
(helps on systems that do not honor the set-gid bit for directories)
+ a -U switch to skip CVSROOT/passwd for /etc/passwd users when
SERVER_SUPPORT is defined.
+ a CVS_PID environment variable that has the getpid() of the
running cvs program.
+ a patch to do_verify that lets the message be rewritten.
This appears to allow the editinfo and/or verifymsg scripts to
update the message for the user. Useful if your scripts are
pulling in information from a bugtracking database or the like.
+ a CVSROOT/options file that is parsed for global options of
tag= tagexpand= umask= and dlimit= (well, the last two are for
OpenBSD).
+ support for CVS_LOCAL_BRANCH_NUM so that CVSup may be used to
have distributed repository copies with local modifications.
+ a fix to diff.c to check that the file is !RCS_isdead()
+ a new cvs_temp_name() variant function for filesubr.c that
supports mkstemp() for FreeBSD
+ support for CVS_OPTIONS read before ~/.cvsrc
+ new rcs_keyword members KEYWORD_CVSHEADER and KEYWORD_LOCALID
with a new flag in the struct rcs_keyword called expandit
+ a patch to update.c:update_fileproc() to send the date to the
RCS_getversion()
+ support for update -r BRANCH_NAME -D"yesterday" which is very
useful also appears to exist.
I think it would be worthwhile to take a look at getting most of
these patches added into the mainline cvshome.org version of cvs.
Enjoy!
-- Mark
>From: Gerhard Sittig <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: diff in commit message (was: Multiple-line log message)
>Message-ID: <[EMAIL PROTECTED]>
>Date: Sun, 29 Oct 2000 09:00:28 +0100
>
>On Sat, Oct 28, 2000 at 22:30 -0400, Larry Jones wrote:
>>
>> [ ... ] I have no idea what the FreeBSD folks have done to
>> CVS, but it appears that they have at least added a global
>> option. To my knowledge, they've made no attempt to get input
>> from the CVS developers or share their changes with us.
>
>For a quick overview here's what I could dig up after you
>implanted the feeling in me that "FreeBSD's CVS is somewhat
>different from the standard CVS":
>
>There's a file /usr/src/contrib/cvs/FREEBSD-upgrade (if only I
>had the bookmark around with the web frontend to the FreeBSD
>source repo -- I can provide it on Tuesday) with the most
>important section for you at its end:
>
>-----------------------------------------------------------------
>...
>Current local changes:
> - CVS_LOCAL_BRANCH_NUM environment variable support for choosing the
> magic branch number. (for CVSup local-commit support)
> - CVSREADONLYFS environment variable and global option -R to enable
> no-locking readonly mode (eg: cvs repo is a cdrom or mirror)
> - the verify message script can edit the submitted log message.
> - if pserver username is "anoncvs", implicitly use a password of "anoncvs".
> - CVSROOT/options file
> - Variable keyword expansion controls including custom keywords.
> - $ CVSHeader$ keyword - like Header, but with $CVSROOT stripped off.
>-----------------------------------------------------------------
>
>> [ ... ] you may want to suggest it (strongly!) to whoever is
>> working on CVS for FreeBSD. You may also want to suggest that
>> they communicate a bit better with the CVS developers.
>
>I copied your request for feedback to [EMAIL PROTECTED] who seems
>to maintain the cvs contrib package.
>
>FYI: FreeBSD's -STABLE branch comes with cvs 1.10.7, -CURRENT
>has imported 1.11 lately.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs