Re: Sparse updates
On Wed, Nov 10, 2010 at 8:41 AM, Daniel Shahaf wrote: > Sounds useful to me. I've submitted the feature request: http://subversion.tigris.org/issues/show_bug.cgi?id=3748 Thanks, Klaus
Re: Sparse updates
On Wed, Nov 10, 2010 at 06:41:41PM +0200, Daniel Shahaf wrote: > Klaus Ganser wrote on Tue, Nov 09, 2010 at 21:19:24 -0800: > > Hello, > > > > I have a simple feature request for the svn update command, so I'd > > like some feedback on the utility of this feature. In the past, I've > > Sounds useful to me. See also https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/svn-viewspec.py
Re: Sparse updates
Klaus Ganser wrote on Tue, Nov 09, 2010 at 21:19:24 -0800: > Hello, > > I have a simple feature request for the svn update command, so I'd > like some feedback on the utility of this feature. In the past, I've Sounds useful to me. > wanted to perform a sparse checkout of several different parts of a > repository, so I've started by checking out the root using > --depth=empty: > > svn co --depth=empty svn+ssh://svn.example.com/trunk/ trunk/ > > From here, if I wanted to download the contents of /trunk/a/b/ and > /trunk/c/d/e/ without any extraneous files or directories, I would > have to first check out all of the intermediate directories in the two > paths explicitly: > > svn up --depth=empty trunk/a/ trunk/c/ > svn up --depth=empty trunk/c/d/ > svn up trunk/a/b/ trunk/c/d/e/ > > What I'm proposing is that svn update have a --parent flag that would > perform these intermediate updates as necessary for the requested > update paths, much like mkdir. > > Thanks, > Klaus
Sparse updates
Hello, I have a simple feature request for the svn update command, so I'd like some feedback on the utility of this feature. In the past, I've wanted to perform a sparse checkout of several different parts of a repository, so I've started by checking out the root using --depth=empty: svn co --depth=empty svn+ssh://svn.example.com/trunk/ trunk/ >From here, if I wanted to download the contents of /trunk/a/b/ and /trunk/c/d/e/ without any extraneous files or directories, I would have to first check out all of the intermediate directories in the two paths explicitly: svn up --depth=empty trunk/a/ trunk/c/ svn up --depth=empty trunk/c/d/ svn up trunk/a/b/ trunk/c/d/e/ What I'm proposing is that svn update have a --parent flag that would perform these intermediate updates as necessary for the requested update paths, much like mkdir. Thanks, Klaus
