[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[REQ] WC-only properties (local:)

From: Kevin Ballard <kevin_at_sb.org>
Date: 2004-09-29 10:31:44 CEST

I had an idea for a feature I'd love to see implemented but I haven't
had enough time to learn about the internals of SVN to implement it

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).

My solution? A separate prefix for unversioned WC-only properties,
properties that don't get committed to the repo. This would be
'local:'. And anything starting with 'local:svn:' could override the
respective 'svn:' property (although in the case of svn:ignore it might
want to append instead). That way I could add my own paths to
svn:ignore or override the svn:eol-style properties without affecting
the repository and without screwing anybody else up.

Any comments or suggestions?

Kevin Ballard

  • application/pkcs7-signature attachment: smime.p7s
Received on Wed Sep 29 10:32:11 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.