On Wed, Mar 25, 2009 at 22:07, Hyrum K. Wright
<hyrum_wright_at_mail.utexas.edu> wrote:
> On Mar 25, 2009, at 4:01 PM, Mark Phippard wrote:
>
>> Given that he said lesson.exe I assume this is Windows and we do not
>> support symlinks.
>>
>> With 1.6 we so support svn:externals for files though. So it could be
>> added just in one place and referenced in others.
>>
>> With all the stuff we are doing around hashes and rep-sharing etc. It
>> is an interesting idea. What if the client told the server the
>> checksum of what it was sending and the server just said "don't bother
>> I already have one of those"?
>
> That thought had occurred to me, also. An intriguing idea, to be sure.
The file external could work pretty well, and is available in 1.6.
In 1.7, we'd definitely know it is the same file because we'll be
storing the pristine version on the client, indexed by its checksum.
We might be able to take advantage of that during the commit process.
Another approach in 1.6 that could work is to take advantage of
knowing the protocol steps used. He could add and commit the
lesson.exe to one directory. Then use "svn copy" to make copies of it
to the other directories. At commit time, svn *should* tell the server
to simply copy the file to the other directories. It shouldn't upload
it again.
Cheers,
-g
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1429825
Received on 2009-03-26 14:13:30 CET