On 9/24/2013 12:47 PM, Quoth Ben Fritz:
> So, there's no longer a need to ever set those properties on any
> subdirectories at all, if they're using the same value for them?
If every user is using a 1.8 or higher client, correct.
If some users are using pre-1.8 clients *and also* using partial
checkouts then they'll "miss" the properties unless they have been
copied to whatever directory they actually checked out as their root.
But this should hopefully be a small subset (and getting smaller as
users upgrade). In some environments it may be guaranteed zero size.
> But don't make the mistake of thinking people don't check out
> partial projects!
That wasn't my argument; I was saying that people should generally not
be checking out *arbitrary* subfolders. Either they will be checking
out the project root or they will be checking out one of a reasonably
small number of "sub-roots" (eg. the project docs root), which should be
known in advance to the project admin as reasonable subdivisions of the
project.
(Note that I'm only talking about checkouts for the purposes of
modification and commit-back. Read-only checkouts don't matter in this
context as the ignore/bugtraq properties etc are mostly only interesting
at commit time, or are fairly harmless when missing if no commits are
intended.)
Given those assumptions:
- if a project can guarantee (or at least be reasonably assured) that
they will only be used with 1.8 clients, then there is no reason to copy
the properties anywhere, because the client will find and cache the ones
in the parent folders of the repository anyway.
- if a project wants to be compatible with pre-1.8 clients and
partial checkouts, then the project admin can *manually* copy those
properties to the expected "sub-root" locations, but the default
behaviour for every other subfolder should be to not have a copy of the
properties (as this introduces needless and potentially harmful redundancy).
Only if my assumption is false and people do really want to be able to
randomly check out *any* subfolder in a repository on pre-1.8 clients
does TSVN's current behaviour make any sense. And while I don't deny
that there's probably *some* people who want this, I hope that it's a
small minority sufficient to justify removing the auto-copying.
Or that at the very least, TSVN should have an option that configures
whether it copies those properties or not (which I would prefer defaults
to "not", but I would be happy as long as it's there).
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3065128
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-09-24 03:41:10 CEST