On Mar 4, 2004, at 12:16 PM, email@example.com wrote:
> "TBrowder" <firstname.lastname@example.org> writes:
>> Users want .svnignore files (not a manual update of prop lists)
> Are you using "users" to mean "I"? :-)
> Seriously, I haven't heard of this being a problem until now, but
> maybe I just didn't see the particular emails you're thinking of.
> It's hard to tell (from the above) how the properties are less useful
> or less convenient than .cvsignore files. I haven't found there to be
> any important functional difference in my daily usage.
I have a request from a potential user for .svnignore files. The
reasoning behind this is that the project does not impose any
particular set of build tools or IDE contraints, so rather than every
user setting every permutation in svn:ignore, they add a local, ignored
svnignore file. Presently they do this with cvs by not having a
.cvsignore file at the top level, and having the user create their own,
put .cvsignore in the list of files to be ignored, and not commit any
of them explicitly.
Its the 'not commit explicitly' that bites subversion, since any commit
based on the root directory will also commit the user's changes to
svn:ignore. Ideally, in an environment where the build tool is constant
but the user's choice of IDE changes, you could have both a svn:ignore
property set to include intermediate files from the build, and a
.svnignore file as a 'local' user addendum for ignoring project files
created by their IDE.
>> Users want svn to recognize at least one environment variable like
>> CVSROOT to point to the repository (not some long URL)
> Others have already answered this very well.
Yes, i haven't seen a need for a SVNROOT - checkouts are rare, and
expansion of this property would make it confusing whether a user is
operating against a local wc file or the repository on the
Received on Thu Mar 4 21:01:39 2004
- application/pkcs7-signature attachment: smime.p7s