> Hi there :)
> A bit of introduction. Now there are 2 excludes - global and local.
> Globals are useful in my case - 100+ projects which are moving slowly
> to svn+tsvn, but it's obvious that the locals are better in long term.
> To add a project & setup excludes now involves (correct me if I'm wrong):
> 1. analysing the project, making a notepad (textpad, emeditor, etc)
> list of all extensions and directories that are not supposed to go in
> 2. clean the project, be carefull not to miss anything from the "list" above
> 3. import the project
> 4. delete the project
> 6. checkout the project
> 7. set the svn:externals to the folders
> 8. commit the project
Yes, it is a bit long winded. There is another way, which is a bit easier.
1. Create a new directory in repo browser to hold your project
2. Checkout this empty folder onto your PC
3. Move/copy your existing project into this folder
4. Add the project files/subfolders to subversion
It is not much easier, but it saves one set of network traffic because
you just do Add instead of Import/Checkout.
> Speaking of excludes, they are mostly common per project type. I.e.
> projests with MSVC have one "set" of temporaly files, the ones made
> with Delphi - another one and so on. So what if you are able to create
> a list of such "sets" in TSVN, i.e.:
> MSVC: *.idl *.dll *.exe ....
> DELPHI: *.whatever ...
You can save such a list to a text file and just paste it into the
> Then, when you are going to import some folder, in the "Import" screen
> being able to select one of those lists (and edit it if needed) and in
> the best case - the list gets stored as svn:externals for this folder
> and below (if checked).
> The steps of adding a new project now will be:
> 1. Import it.
> Hope u like the idea
Having a more friendly GUI import sounds like a good idea. But, making
it work in the general case is not so easy. Where would you apply those
ignore properties? To the top folder or to every folder recursively?
What if different folders need different ignore lists (a common
requirement)? Where are you going to set the externals? Maybe *you*
always set them in the same place, but others may not.
Also, there are some developments going on in Subversion (search the svn
list for "svn takeover") which may help with this. If we do something
now, it may be redundant when SVN 1.3 comes out, so I think we should
wait a bit to see what is coming.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Aug 26 14:00:05 2005