"Trott, David" <[EMAIL PROTECTED]> writes:
> For various reasons (such as external vendors only releasing binaries) we
> use CVS to control .class files, other people may wish to store other binary
> files in CVS.
>
> It may cause a problem for some people if these binary files were added to
> the ignore list.
That can be said for every type of file already on the ignore list as
well. That's what the -I ! option is for. I think the idea is to get
things on there that are normally generated as a part of the build
process; if you've got things that aren't built locally but are on the
list, then you need to be aware of it and take appropriate action.
(P.S. - maybe there should be a "-I-" counterpart to "-I", which would
mean "*Don't* ignore files matching the following pattern". This way
somebody who wanted to "pay attention to" a single file type could
just do, eg "-I- *.class", rather than "-I ! -I *.lib -I *.o -I *~
...."
> David
>
> "Larry Jones" <[EMAIL PROTECTED]> wrote in message
> news:<[EMAIL PROTECTED]>...
> > Derek R. Price writes:
> > >
> > > Is there a policy on adding file names to the default ignore list?
> >
> > Not really, and it does seem to be a bit dated. In addition to ID as
> > suggested by Assar Westerlund, Pavel Roskin submitted a patch on 30 Jan
> > 2001 that proposed adding:
> >
> > .deps Automake
> > .depend Linux, MC and possibly others
> > .libs Libtool
> > *.gz Gzip
> > *.bz2 Bzip2
> > *.flags Linux
> > *.la Libtool
> > *.lo Libtool
> >
> > and I'd also suggest adding:
> >
> > *.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
> > *.info* GNU info file
> >
> > Perhaps a discussion on info-cvs is in order to see what people think
> > about these or other additions?
> >
> > -Larry Jones
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
