[cvsnt] Re: RC4 glitches or features...?

Oliver Giesen ogware at gmx.net
Tue Aug 16 02:52:31 BST 2005

Tony, did you notice these in my post from yesterday?

Oliver Giesen wrote:

> Creating an Entries.Static in the top-level CVS folder did not give
> the desired effect (as I should have expected as I realize now). So,
> is using cvs -f the only way to get what I want here?

(this was about how to update only selected directories when the
server's cvsrc contains up -d)

> Some more strange things I found while updating back and forth between
> various sticky tags and the trunk from the CVSNT repository:
> - I never ever see a single [P]atched line being output. All files
> appear to be [U]pdated always.

Has CVSNT just simplified the output or is it really always fetching
all files in full nowadays?

> - Some files fail to update to the desired sticky tag with rather
> strange results and error messages. Apparently these are files that
> have previously been renamed.
> Starting out with a clean trunk checkout of the cvsnt module,
> executing the following commands in the windows-NT subfolder should
> illustrate this:
> cvs up -lrCVSNT_2_5_02_2057
> type CVS\Entries
> cvs up -lrCVSNT_2_5_02_2054
> type CVS\Entries
> dir
> del /q *.*
> cvs up -lrCVSNT_2_5_02_2054
> type CVS\Entries
> cvs up -lA
> type CVS\Entries
> dir
> If you want I could post the full session log including my output but
> so far this happens consistently enough for me that I don't think this
> will be necessary.

This still happens with the 2060 build.


----  ------------------
JID:  ogiesen at jabber.org
ICQ:  18777742     (http://wwp.icq.com/18777742)

More information about the cvsnt mailing list