project options (was: Re: cmd line stuff)x

On Wed, Oct 18, 2000 at 01:09:57PM -0400, Jonathan S. Shapiro wrote:
>...
> 4. [Minor addendum] It also shouldn't have been in required in *all* the
> .cvsignore files. You certainly need to be able to specify such things on a
> file by file or directory by directory basis, and .cvsignore files work fine
> for this, but there should also have been a way to specify this globally on
> a per-project basis, and in such a way that *anyone* who checked out the
> project would be subject to the same rules. In CVS, this could have been
> done by creating CVS/Options files (just a thought balloon -- not a
> proposal).

I believe that we're going to have much better mechanisms for per-project
configuration. First, we have the httpd.conf file. Alternatively, we have
properties on the root dir of the project/repository.

The property one is nice because it provides for remote configuration. It
also means that we can apply the pattern on a per-dir basis.

Why use ".cvsignore" when you can set the SVN:ignore-extensions property?

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/