[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Suggestion: Default repo and working directory path

From: Udo Eberhardt <Udo.Eberhardt_at_thesycon.de>
Date: 2006-09-13 08:28:19 CEST

We have many projects stored in one repository. People quite often have
to do a checkout to start working on a project. To keep things simple,
by convention we use the same directory structure on the local disk as
in the repository. To make daily work more comfortable and to avoid
mistakes caused by typos, the following feature would by nice:
- TSVN provides an (optional) setting which defines a default repository
URL. Every time I launch the repo browser on a non-versioned directory
this is set as the default URL in the URL window which pops up. I can
still modify it, if desired. Today the URL is set to none by default
which requires me to enter an URL or select one from the combo box.
- TSVN provides another (optional) setting which defines a local
directory path (absolute path) which is associated with the default repo
URL. When I choose checkout on a directory in the repo browser then TSVN
computes a default checkout path based on the given absolute path and
the current subdirectory in the repository. This default path is shown
in the Checkout dialog. I can still modify it, if desired. Today the
checkout directory is set to empty by default which requires me to enter
the local path manually on every checkout.

Maybe applying this default URL to local path association is also useful
for other commands. Checkout is just the most obvious to me.

Such a feature would make TSVN easier to use, especially for former
SourceSafe users. SourceSafe maintains an association between a data
base path and a local path.

Udo Eberhardt

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Sep 13 09:48:49 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.