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

[TSVN] Re: 1 feature request; 1 bug

From: Molle Bestefich <molle.bestefich_at_gmail.com>
Date: 2005-03-25 02:36:16 CET

>>>>= Bug:
>>>>It's possible to manually enter a destination directory for exports.
>>>>If a non-existing directory is entered, TSVN should either create the
>>>>directory silently or tell the user that the directory does not exist.
>>>> Currently it exports your data to C:\Documents and Settings\whatever
>>>>instead.

>> The CL silently creates the destination directory specified (though it
>> only automatically creates 1 level deep - not sure if this is changed
>> in SVN trunk, could be).
>
> Are you using a nightly build?

2870.

> Because even though I can enter a wrong
> path in the dialog, TSVN still uses the last selected path which exists.

Correct, that's the behaviour I'm seeing.

I tell TSVN to export to X:\poopoo and it instead exports to
C:\Documents and Settings\whatever\whatever.
The right thing to do is to either:
 - 1. tell me "you're a baboon. try again. this time tell me about a
directory that exists." or
 - 2. silently create the destination folder just as the CL client
does. (provided it's not
x:\doesnotexist_level1\doesnotexist_level2... in which case an error
should be shown..)

Stuffing the files in some random folder where I'll never find them
again because I dismissed the dialog that tells me where TSVN decided
the files should go (instead of the path I entered ;-)... I'll stop
now) doesn't seem right. The only time I want that is if I select a
folder from the list, and then again, only if I do not enter something
in the text field afterwards..

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Mar 25 02:36:46 2005

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.