I'm not sure where to post a suggestion for future versions but this is
definitely not a "bug". If this isn't the place or if you guys have
already thought of it, please let me know.
I know that svn is typically used for source code control and not binary
files, so this may not be a common usage. I have a library of
multimedia that I maintain in version-control along side its source
files. Sometimes I have a situation where I have updated some
multimedia "player" that is used in several locations. Then, I updated
all the directories where the player resides with the newest player.
Then I commit the revision. Subversion proceeds to then upload the same
file over and over again to the repository. It seems that the
client/server communication could be a little smarter and only send a
file once if it is the same file.
As I am writing this, I am committing a media directory that contains 57
"lessons": media/lesson1, media/lesson2, etc... I have a 5MB file
called lesson.exe in each of these that I had to change. I have to keep
the file in each directory because my company often distributes a single
"lesson" and not the entire collection.
I am not familiar with the protocol on the back end of subversion but I
assume it goes something like this:
put file1 at /xyz
put file2 at /asdf
put file3 at /xyz/asdf
Let's assume file1 and file3 are actually the same binary data. Maybe
you could just add some sort of back reference that the server could
understand like this:
put file1 at /xyz label=A
put file2 at /asdf
put [A] at /xyz/asdf
The client would have to be smart enough to determine which files match
and could inform the server in this manner. Obviously, this is only a
suggested implementation as I am not familiar with the protocol.
Thanks (if nothing else, just for reading this),
Phil
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1419789
Received on 2009-03-25 21:48:13 CET