I think you could argue that in general, .log files are something which are generated by running programs (in much the same way that, say, file.o files are generated by the compiler) and something that you wouldn't want in a CVS server at all.

I also think that it's very unlikely that you'll want to keep a maven.log in a file anyway.

Of course, bear in mind that the Attic are there-was-a-log-but-we've-deleted-it-from-CVS anyway, so there's only really two log files, and both of those are in the 'examples' directory.

You might like to check with merlin, but if they're cruft they may want to delete them as well :-)

Alex.

On Friday, Aug 15, 2003, at 00:25 Europe/London, Brian Behlendorf wrote:


[minotaur] 4:15pm CVSROOT > locate maven.log,v | grep home/cvs
/x1/home/cvs/avalon-excalibur/Attic/maven.log,v
/x1/home/cvs/avalon-sandbox/merlin/merlin-platform/examples/afs/ simple/maven.log,v
/x1/home/cvs/avalon-sandbox/merlin/merlin-platform/examples/afs/ simple-servlet/maven.log,v
/x1/home/cvs/jakarta-commons/logging/Attic/maven.log,v


If you can convince the avalon-sandbox folks they don't need it, then we
could enable it globally.


        Brian

On Fri, 15 Aug 2003, Jason Dillon wrote:
maven.log is in cvs?  I agree with the others in this case.  My point
was rather than litter up the codebase with .cvsignores to simple use
globals.

--jason


On Friday, August 15, 2003, at 05:50 AM, Brian Behlendorf wrote:

On Fri, 15 Aug 2003, Jason Dillon wrote:
Whats the global cvsignore?

CVSROOT/cvsignore

We can not add maven.log, .project, and .classpath to the global .cvsignore when there are so many ,v files in the cvs repository for files with those names.

        Brian





Reply via email to