On Thu, Mar 29, 2012 at 6:19 AM, Paul Coulson <paul_at_coulsonweb.co.uk> wrote:
> I have a legacy repo structure that has many projects with their own tags
> and branches folders.
>
> Users check out the whole structure as there are common lib references etc,
> but they don't need to see the full contents
> of tags or branches folders, which can be massive.
>
> I would like a property svn:inhibit (similar to svn:ignore) set on the root
> folder
> that limits the checkout depth for a folder anywhere in the tree that
> matches the inhibit list.
>
> By setting as a property, a new checkout will inherit this property and
> limit the checkout depth for the named folders as required.
>
> Users can then checkout particular tag versions as normal if they require
> past versions, but an update at the root will not checkout tags or branches
> by default.
>
> IMHO this will make the behavior of a tag more like what the SVN manual says
> is just a "user friendly name for a revision".
> You wouldn't want to check out all revisions on the trunk, so why check out
> all revisions for tags by default?
>
> This would be a really cool improvement, as I see the problem has been
> mentioned many times on SVN groups.
Your real issue is that you aren't using externals to pull in the
component references. Do that and you only need to check out specific
project trunk or branch/tag revision you want at the top level and
your self-inflicted problem goes away.
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2012-03-29 17:07:51 CEST