Hi guys
We want to add a feature to Tortoise SVN to allow selective update from
the repository, and we wanted to discuss this first here, since we think
it might be possible that other people is interested, and we'd like to
have this integrated in TortoiseSVN if possible. Let me know what you
think about it.
The selective update feature might seem not so useful for source code,
but it has a lot of sense when you're managing big files in the
repository in a large project. In this way, a user does not need the
whole repository to work. The type of files we're talking about are 3d
geometry files, texture files, animation files, photoshop files, etc.
Some of them are dozens of megabytes long. Doing selective updates can
increase a lot our productivity.
The idea would be to be able to browse the remote repository and select
what we want to download (/ update). Although it might seem that this is
already implemented using the update in the inner folder, the problem
occurs when you want to update a folder that does not exist in your
working copy (since it was created in a higher revision). For example,
imagine Bob is at revision 1:
Levels
Maps
Assets
|--+ Nature
| |--+ Rocks
| | |--+ Rok01
| | | |--- rock.3d
| | | |--- texture1.png
| | ---+ Rok02
| ---+ Sea
|--+ Fabrics
But the repository is at revision 20:
Levels
Maps
Assets
|--+ Nature
| |--+ Rocks
| | |--+ Rok01
| | | |--- rock.3d
| | | |--- texture1.png
| | |--+ Rok02
| ---+ Sea
| |--+ Tree
| | |--+ Mediterrainean
| | | |--+ BotHomOak
| | | | |--+ BotHomOak1
| | | | |--+ BotHomOak2
| | | | |--+ ...
| | | | |--+ BotHomOak10
| | | |--+ CercisSiliquastrum
| | | | |--+ ...
| | | |--+ FicusCarica
| | |--+ Caribean
|--+ Fabrics
Bob needs to work in BotHomOak1, the only way is update completely the
Nature folder, since Bob does not have the "Tree" folder locally. But if
he does that, he will have to download all the assets in "Tree", and
these might be hundreds of megabytes more. One way is to update non
recursively the folders Nature, Tree, BotHomOak, and then BotHomOak1.
This is the process we want to make easier.
One idea is to modify the repoBrowser tool and add some options to do
updates on a working copy. This update tool would handle if the
files/directory are already in the working copy or not. The reason to
use the repoBrowser is because it already has a tree view of the
repository and explores the server on demand (when a folder is expanded
in the tree). Another option could be through the check for
modifications combined with the option check repository but this does
not have the two features mentioned before, it is flat and checks
differences in the whole repository.
Comments or better ideas are welcomed before starting to work on it :)
regards
Mateu
Received on Wed Mar 7 18:54:06 2007