Matt Dowding writes:
>
> My CVS client does not seem to support the tracing option (i.e. cvs co -t
> <module> fails as it does not like the -t).
That's because it's a global option that goes before the command name,
not after it:
cvs -t log <module>
> The Entries.Log file looks like this :-
>
> D
>
> The Entries.Log file looks like this :-
>
> A D/solaris-sparc////
I assume the first file should be Entries. If so, that would be
appropriate for a directory containing a single subdirectory
(solaris-sparc). Is that correct? The Entries file does not stand
alone; if there is an Entries.Log file, it contains changes to the
Entries file that need to be applied before using it.
> One thing I have discovered is that the files appear ok (and cvs status
> works) if I explicitly request a recursive checkout (cvs co -R <module>).
Recursion is the default for checkout (unless you have a ~/.cvsrc file
that overrides it). Explicitly asking for recursion has absolutely no
effect if it's the default, so I don't think that's what really caused
the difference. We really need the trace file to figure out what's
going on.
-Larry Jones
I'm crying because out there he's gone, but he's not gone inside me. -- Calvin
_______________________________________________
Bug-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/bug-cvs
