[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Sparse checkouts suggestion

From: Branko Čibej <brane_at_apache.org>
Date: Wed, 13 Sep 2017 04:52:36 +0200

On 13.09.2017 04:22, Paul Hammant wrote:
> Compared to Perforce's client-spec, Subversion's sparse checkouts are
> quite cumbersome:
>
> svn checkout http://svn.apache.org/repos/asf/subversion
> --depth=immediates
> cd subversion/trunk
> svn update --set-depth infinity
> cd ../tags
> svn update --set-depth immediates
> cd 1.7.7
> svn update --set-depth infinity
>
> .. and similar.
>
> Could Subversion follow Perforce and allow an _alternate_ mechanism
> that leveraged include and exclude globbing paths?
>
> Maybe in the root of working copy, the contents of a /special/ file
> could be honored:
>
> .sparse_mappings.txt
>
> Sample contents:
>
>    exclude **/*
>    include trunk/**/*
>    include tags/*
>    include tags/1.7.7/**/*
>    
> Where the end user to do svn-up from root (after that file changed),
> and assuming 'svn st' were 'clean', the working copy would reshape
> itself. Specifically directories would appear and disappear, and that
> NOT necessarily be subversion adds or deletes - it'd feel the same as
> permission changes within the directory tree.  Of course different
> teammates with the same checkout may see entirely different things
> (depending on the lines within their .sparse_mappings.txt

This is an old idea. If you want to implement it, a file is not the
right place for the view definition; a property on a directory might be.

-- Brane
Received on 2017-09-13 04:52:43 CEST

This is an archived mail posted to the Subversion Dev mailing list.