On Mon, Jul 26, 2010 at 9:59 PM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Mon, Jul 26, 2010 at 05:30:56PM +0100, Bolstridge, Andrew wrote:
>> If you have a directory full of source files,
>> and it contains a sub-directory full of almost-never-changing, large
>> binary files, then it would be great to initiate an export and have it
>> recognise the binaries haven't changed and so don't need to
>> re-downloaded over the top of the existing files.
> svn update does just that. It only needs the .svn meta data to work.
> In 1.6, you need to exclude more than one .svn directory when archiving the
> working copy. In 1.7, the meta data will be in a single .svn dir at the root
> of the working copy, which should be even easier to deal with.
> I don't see added value in making svn export do that, because svn export
> would have a much harder time to detect non-modified files than update
> ever will.
+1. My thoughts exactly.
A year ago I was actually thinking about a similar feature: "wouldn't
it be nice if export was a little smarter, downloading only the files
it needs, a bit like update but without maintaining a WC (because wc-1
working copies are slow with all the locking, the per-directory meta
data is cumbersome if you don't really need a WC, ...)".
I think it could have been a nice feature in the wc-1 world. But now
that WC-NG is just around the corner, I don't think it's worth it. It
will be much easier and (hopefully) just as fast to use a 1.7 working
copy, and ignore the single .svn meta data directory if you want to.
Received on 2010-07-27 00:49:29 CEST