RE: Update-Only Checkout Enhancement
From: Mark Kneisler <mark.kneisler_at_tceq.texas.gov>
Date: Wed, 11 Dec 2013 16:21:54 +0000
I think making the pristine files optional would work for me.
Here's an idea.
Instead of having pristine copies of all files, how about adding to the pristine directory only when a file is changed?
From: Mark Phippard [mailto:markphip_at_gmail.com]
On Wed, Dec 11, 2013 at 10:46 AM, Mark Kneisler <mark.kneisler_at_tceq.texas.gov<mailto:mark.kneisler_at_tceq.texas.gov>> wrote:
For these environments I have a few requirements:
I'm fairly certain that this functionality is currently not present, but I think there are many installations where this would be valuable.
I'd like to create an enhancement request, but according to the website it was recommended that I post to this mailing list first.
Pristine files do not exist solely so you can edit files. It is convenient they exist so that you can diff your changes or revert your changes without needing to contact the server, or even be online, but obviously those commands could be made to use the server for that and simply require a connection when no pristine is available.
The main reason the pristine files exist is so that the client and server can exchange deltas with each other and minimize network traffic. This is just as true for update as it is for commit. One of the original mantra's for the 1.0 release was "disk is cheap, network is expensive".
There is an existing request in the system for making these files optional:
http://subversion.tigris.org/issues/show_bug.cgi?id=525
There is also an existing request for storing the pristine files in compressed format:
http://subversion.tigris.org/issues/show_bug.cgi?id=908
-- Thanks Mark Phippard http://markphip.blogspot.com/Received on 2013-12-11 17:22:31 CET |
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.