This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: cvsignore
Marius Vollmer <mvo@zagadka.ping.de> writes:
> "Greg J. Badros" <gjb@cs.washington.edu> writes:
>
> > > Why? I think that .cvsignore is a property of the module to which it
> > > belongs. The module owner (the FSF in this case) can specify the list
> > > of files which are to be ignored in the current module. This list is
> > > valid for every environment in which the module may be used.
> >
> > Right, and that is my belief, too, but there was concern about
> > developers who believed that .cvsignore should be reserved for the user
> > to specify his/her preferences.
>
> I'm one of those and I still don't think .cvsignore should be in the
> repo. But I guess it's hard to come to a conclusion as peoples
> experiences with CVS, their expectations how they want it to work, etc
> vary widly. So I hacked CVS to support the idea of having it both
> ways.
>
> Everybody who wants to have his personal .cvsignore file can use the
> hacked CVS (patch below) and .cvsignore just stays in the repository.
>
> The patch works like this: when the environment variable CVSDOTIGNORE
> is set, it specifies the file name of the per-directory .cvsignore
> file. When that file exists, CVS uses it instead of the usual
> ".cvsignore". When the file does not exist, it tries ".cvsignore"
> instead. Note that CVS does only use one per-directory file.
It'd be great if CVSDOTIGNORE could be a semi-colon separated list of
files to ignore so you could ignore .cvsignore *and*
.cvsignore-personal. Also, it'd be great if you sent this along to the
CVS maintainer w/ a brief description of the issue-- it's something that
CVS should just handle better, and yours (w/ the one tweak) seems like a
great way to go about it.
<snip>
Greg