If the 'checkout' logic can tell the server to not send some files, then so can the 'update' logic. It's just a matter of making it remember to do that. (i.e., having the exclude pattern persist somewhere and used by the 'update' command)
Autumn wrote on Fri, Sep 10, 2010 at 08:27:34 -0700: > Cool, that hadn't occured to me. That could mean that no structural > changes are required to the .svn format -- only a code change to the > checkout logic to preemptively create the exclude entries. > > I'm not sure how it would handle the case where someone else adds new > files which match my pattern, for which no svn_depth_exclude entry yet > exists. > > Ideas? > >> I think under the hood, such a --exclude option would be implemented by >> setting the depth of the files-matching-the-pattern to svn_depth_exclude. >> So I'm asking if the desired feature is to be able to set that depth at >> checkout time, before the files are fetched even once. >
