Stefan Küng wrote:
> the-moog wrote:
>> I have been tasked with migrating/interoperating from MKS to SVN, this
>> process will take some time, even years.
>> There is no way to integrate both applications fully, so one way round
>> it is to invent SVNLinks (see my other post)
>> I have written a rather complicated batch file that allows a link to
>> be placed, such that clicking the link checks out the contents of that
>> link to the current folder.
>> But at the moment, the tsvn: links check out only the HEAD. I have
>> made the batch file understand a bookmark in the link file (a standard
>> windows url file) but it would be nice if TSVN did this itself as it
>> would be useful to others.
>> e.g. Click this link to use TSVN to check out lastest stable version
> Why don't you create a tag for the latest stable version?
>> 1: It returns 0 as an errorlevel, even when there is an error, it
>> should return the same as svn
> Sorry, TSVN is *not* a command line utility and can't return proper
> return values.
Values return from main() or the win32 API call ExitProcess() are
returned correctly when a win32 GUI application is called from the
command line. (Lower 8 bits is all that is used.) At the very
least success/failure - 0/1 should be doable.
>> 2: /command:checkout /path: seens to generate inconsistent results,
>> sometimes the leaf folder in the repo is appended to whatever path you
>> specify, sometimes not.
>> 3: There is no way of returning the version of TortoiseSVN to cmd
> Yes, because TSVN is not a cmd utility, it's a GUI client and does not
> have a console at all, so it can't print/return anything on the
> (non-existing) console.
A GUI app can allocate/reuse the console when launched from
the command line. Takes a little work though...
It is really nice to be able to use TortoiseProc in scripts
to be able to prompt users in a graphical form for things
like passwords, etc. Since the command line utils and
TortoiseSVN store this info differently, it is almost essential.
For work, I wrote a simple interaction between Rhapsody and
TortoiseSVN. It needs to lock multiple binary files for
certain operations, and an user would normally have no clue
which ones to lock, so using TortoiseSVN directly is not
feasible. Having TortoiseSVN prompt for things like a password
makes in interface pretty seamless.
(Unfortunately I needed to do a propset via a command line,
so the users must install both tools, and potentially authenticate
So short story, I think a command line option for tortoiseSVN is
essential, and I really appreciate what is already available!
(And hopefully we can even improve it.)
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-09-10 02:40:45 CEST