[cvsnt] How to get the new admin files in build 2214 into existing CVSROOT?
Mike Wake
mike.wake at thalesgroup.com
Wed Jan 18 11:30:51 GMT 2006
Bo,
I have in the past run cvs init on an existing repository. This added
any new files while leaving any existing file in place. If you do this
you miss out on any new documentation/comments at the top of the
existing files so you probably want to do a diff between a checked out
version of CVSROOT of the old Repository and a checked out version of a
brand new (ie cvs init) test Repository and merge the relevant changes
in commments as well.
I would suggest that the way you have been doing it is essentially the
way it needs to be done.
Cheers
Mikew
Bo Berglund wrote:
> I have noted that the shadow file is now part of the automatically
> generated admin files in CVSROOT from build 2214.
> This brings up a question I asked before:
> Is there any command that can be used on an *existing* repository to
> bring the CVSROOT module up to date concerning the CVSNT server
> version?
> What I observe is that there are new files popping up along the
> development path but these are unavailable in existing repositories so
> it is not easy to start using them. They show up if one creates a new
> repository with the new CVSNT version.
>
> It would be nice to have a command (possibly in the Control Panel) to
> refresh an existing repository with new files following a server
> version update....
>
>
> /Bo
> (Bo Berglund, developer in Sweden)
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org
> http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
More information about the cvsnt
mailing list