That is a good suggestion, however if I only need to post a change to
one file, why should I have to export the entire directory tree? My
thought was that it would be nice and simple if TSVN supported UNC
export paths, that way I could easily select the files I wished to
export.
Jared Armstrong
-----Original Message-----
From: Kevin Greiner [mailto:greinerk@gmail.com]
Sent: Thursday, January 26, 2006 5:02 PM
To: users@tortoisesvn.tigris.org
Subject: Re: Export capabilities
I would write a batch file that uses the command-line client which
supports UNC paths directly.
Something like:
svn export svn://localhost/code/web \\web1\deploy\web --force
You can download the svn win32 1.3 binaries at the bottom of this page:
http://subversion.tigris.org/project_packages.html
On 1/26/06, Jared Armstrong <jarmstrong@omnispear.com> wrote:
>
> Are there any plans to allow export capabilities for standard UNC
> paths in addition to the existing directory tree? I have staging and
> production paths that I purposely do not keep mapped that I would like
> to be able to export to.
>
> Thanks,
>
> Jared Armstrong
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Jan 27 15:10:49 2006