Kevin Ballard wrote:
> A problem that crops up every now and then is I'd like to add a
> property to a file but I don't want to commit it to the repo. For
> instance, I may have scripts I wrote to facilitate my personal use of a
> project that applies to nobody else. It doesn't make a lot of sense to
> add it to the versioned svn:ignore property since it couldn't possibly
> affect anybody else and that just clutters up the repo with information
> that only applies to a single person. But it's also quite annoying to
> have it show up every time I run an 'svn status'. And this applies to
> other properties as well. For instance, a file may be set to
> svn:eol-style=native but I personally want it set to svn:eol-style=CRLF
> for some unknown reason. If I committed that to the repo, everybody
> would get it as CRLF and that could be disastrous. But if I don't, I
> have the wrong line endings on my end (don't ask me why I'd want CRLF,
> this is hypothetical).
I'll ask the obvious question: why not just create your own branch
and add your properties there?
-Archie
__________________________________________________________________________
Archie Cobbs * CTO, Awarix * http://www.awarix.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 29 16:30:38 2004