On Wed, Nov 7, 2012 at 3:40 AM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
> On Wed, Nov 7, 2012 at 8:52 AM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
>> Paul Burba wrote on Tue, Nov 06, 2012 at 12:01:54 -0500:
>>> Also keep in mind that if you really want to add an ignored file you
>>> can make the file the target of the 'svn add' command. Just like with
>>> the runtime config global-ignores and the svn:ignore property in 1.7,
>>> if the file in question is the explicit target of an add subcommand,
>>> it will be added, no need for . Import works the same way.
>> About the applicability of similar workarounds to svn:auto-props : two
>> options that come to mind are 'svn add foo.py && svn pd svn:eol-style
>> foo.py' and 'mv foo.py ___; svn add ___; svn mv ___ foo.py' (yuck). But
>> the back-of-the-head thought I had was, "But what if we have a process
>> that watches the wc, seeing changes as they happen, that sees the file
>> with the auto-prop in place --- or with the temporary name --- before
>> I had a chance to remove it?"
>> Making 'svn add --no-auto-props' disregard svn:auto-props is
>> a bulletproof solution to the above.
> I haven't tested, but wouldn't something like 'svn add --config-option
> config:miscellany:enable-auto-props=no' do something like that? Or
> does that not override the "repos-default" svn:auto-props?
It doesn't. Runtime config options, including those specified via
--config-dir or --config-option, have no effect on how the new
svn:auto-props property is used.
Paul T. Burba
CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development
> Or if that doesn't work, what about 'svn add --config-option
> "config:auto-props:*.py=" foo.py' ? No idea if that works ... in any
> case it seems very cumbersome ...
Received on 2012-11-07 22:11:20 CET