> On Aug 16, 2016, at 2:13 PM, Adam Jensen <hanzer_at_riseup.net> wrote:
> On 08/16/2016 09:17 AM, Stefan Hett wrote:
>> Just to have this mentioned: Be aware that the working copy (aka: the
>> checked out data of the repository) will have a 2x storage requirement
>> on the data since it will keep a copy of the pristine version of the
>> file in addition to the "actual" file.
>> If this is a concern for your use-case, you could export the files and
>> only use a working copy in cases where you need to commit or reorder files.
> By "export the files" do you mean something like an NFS share of the
> repository, thus bypassing svnserve and the check-in/check-out process?
> That seems like a clever possibility worth remembering, but for now the
> system I am currently building/imagining is headed in a different direction.
He means avoid the 2x disk use by using "svn export" instead of "svn checkout".
>> To clarify: This is purely a client side storage requirement. It does
>> not apply to the storage requirements on the server side.
> To reduce network load, are there any client-side caching options for
> Subversion? Does the svn program account for the files already in the
> working copy (on the local disk) and avoid transferring those files over
> the network during a subsequent check-out [that requires those files]?
Of course Subversion only transfers changes.
> Is it possible to clone or mirror all or part of a Subversion repository?
> <speculative fun> This probably isn't relevant to Subversion, but in the
> system I am imagining it might be reasonable for clients to check-out
> data-sets via torrent connections with other full/partial repositories.
Received on 2016-08-17 06:56:08 CEST