Quoting Pavel Roskin <[EMAIL PROTECTED]>, who wrote:
> Hello, Derek!
>
> > Larry:
> >
> > *.lib DOS/Windows library
> > *.dll DOS/Windows dynamic load library
> > *.sl HP-UX sharable library
> > *.class Java binary
> > *.backup Misc backup file
> > *.dvi TeX output
>
> Fine with me.
>
> > *.info* GNU info file
>
> This would be bad. Some projects keep all distributed files on CVS, even
> those that are generated.
They can still add them, alread .obj .o .a and .exe s are ignored. It
won't make everybody happy, but a least its (self-)consistent.
> There is another issue. For most (if not all) entries in this list, the
> directories with such names should not be ignored, only regular files.
I think this would be great, but when I add the directory "objs" to
my .cvsignore file, would it not be ignored because its a directory?
Not so good... Short of rewiring the cvsignore so you can specify
a file type, I don't think there's much to do about this problem.
> For example, a file named "core" should be ignored. But a directory named
> "core" should not be ignored! I have seen two times people having problems
> importing Linux kernel into CVS because of that.
>
> By the way, I guess there are directories matching *.lib in a few
> projects. It's good to be prepared.
I've done that, our build tools would look at a directory name, and if
it ended in .lib, all the c files in the directory would be compiled
into a library named after the directory. zero maintainance.
--
Sam Roberts <[EMAIL PROTECTED]>
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
