You cannot do it with .cvsignore, since it applies only to files present in the local copy and missing from the repository. Of course you can do piping CVS output through a rather trivial sed script, but in my opinion it is very inconvenient.
Am I missing something? Not really, what I meant was when you have a diff that you created from `cvs diff', you can edit it, and ripout a whole file (say configure) quite easily. I do this all the time, and it takes me a second to do it (you just hit `K' in diff-mode). Well, yes, that is true. On a side note, these can be omitted from the repository as well, the way we do in tar, cpio and cflow repositories. However, here I tend to agree with you that it is better to have gnulib sources in our repository, simply because we have got no control over the way they change in gnulib, and sometimes their changes in gnulib break their usage in the application. gnulib should never break anything, if it does, it is a bug in gnulib and not on our side. The gnulib maintainers are very picky on this point, it is also written in the README. Besides, these files do not change as often as autogenerated files do. Not to be picky, but they have changed more than configure over the past year. Each update of gnulib freaks me out. PS: I'd like to ask our colleagues to share their opinions, too. That is the point of a mailing list. :-) _______________________________________________ Bug-inetutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-inetutils
