2012/1/6 Mark Phippard <markphip_at_gmail.com>:
> On Thu, Jan 5, 2012 at 2:42 PM, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
>> I think most of use-cases can be solved by existing mechanism without
>> inventing something new:
>> 1. auto-props
>> TortoiseSVN already has 'tsvn:auto-props' property . Which used to
>> automatically set properties for added files. It would be nice if
>> Subversion core support this property.
>> 2. ignores
>> We can add svn:global-ignores property to define global (recursive) ignore mask.
> The approach TortoiseSVN and some other clients take does work pretty
> nicely but I also think they reveal the short comings in using
> properties. For convenience, TortoiseSVN does not force you to set
> these properties on every folder and instead will walk to the root of
> your WC to find them, but then this also exposes the problem that if
> you did not checkout the folder that has those properties you are back
> to square one.
As I wrote in this very thread two days ago , this shortcoming
could be solved if the properties for the parent folders were present
in the WC.
Now that wc has a database it could store those properties.
> That is why I believe it makes sense for SVN to
> support it natively using an approach something like described in the
> wiki. Or at least weigh that approach versus using properties within
> the repository. Perhaps properties are the way to add the deferred
> feature of supporting overrides based on path?
I like TortoiseSVN way because
a) it is already known for several years and it works
b) it leverages existing support for path-based security, for svnsync
and dump formats.
If this approach is rejected one could at least mention that it was
considered and write down why it was rejected.
Received on 2012-01-05 22:18:00 CET