Julian Foad wrote:
> Kevin Ballard wrote:
>> D'oh, wrong button!
>>
>> Anyway, svn:ignore is used for other things too, like adding new
>> files and stuff.
>>
>> And this local: idea can be used for other properties too, like
>> svn:eol-style and things like that. Or if I have a script that uses
>> properties of the file and a given property makes sense to be
>> different from user to user (or just needs to be overridden by a few
>> specific users) local: properties could be used there too.
>
> Kevin, you may have a good idea for a useful enhancement. I suspect
> that the reasons you are not getting much positive feedback are:
>
> + other people don't seem to have found much of a need for this yet;
Ankh could actually benefit from local-only properties. Ankh lets the user
decide if he wants Ankh to load for a specific solution. To persist this
choice, we currently create a file in the solution directory, which is
checked upon solution load.
With local properties, we could instead create a local:ankh.load(or
local:ankh:load) property on the solution file and check that when a
solution is loaded. I could also imagine other project/solution specific
settings we might want to store using such a mechanism. I'd rather avoid
littering the project directories with files created by Ankh, especially
when there's already a metadata storage facility available.
I am sure there are also other similar scenarios in which SVN tools could
store working copy-specific metadata using these properties.
--
Arild
AnkhSVN: http://ankhsvn.tigris.org
Blog: http://ankhsvn.com/blog
IRC: irc://irc.freenode.net/ankhsvn
"Gentlemen, you can't fight in here! This is the war room!"
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 3 23:30:56 2004