Todd C. Gleason wrote:
> I had wanted to do this to and come to the same conclusion. In the
> end, we just have to require people to install/upgrade both clients
> at the same time.
That's only really necessary for 'major' upgrades, i.e., if the second
(or first, if we ever get to version 2) version number changes.
Intermediate updates where only the third number changes don't require
updating all clients at the same time.
> One thing that would be helpful would be if there were versions of
> TortoiseSVN installers that included the equivalent CollabNet
> command-line installations. The problems I can see though is that it
> would probably be a technical pain, and it would mean waiting for
> CollabNet's releases, which often trail TortoiseSVN releases by a few
> days. Of course I could imagine releasing the standalone TortoiseSVN
> 1.x.y and then later releasing the equivalent "bundled" TortoiseSVN
> 1.x.y...or releasing with something other than CollabNet binaries.
We've discussed this before, and we won't do that. Because whatever we
bundle, we have to support - and supporting TSVN is more than enough
work already.
> But I doubt the TortoiseSVN team wants to do this, and I don't blame
> you. It's just not that big a deal to save users a few minutes in
> downloading and installation time. Presumably a determined developer
> could even write their own installer to wrap both TSVN and SVN client
> installations as well.
>
>
> On to the specific problem mentioned above...I think I have a similar
> use case. Basically I want to commit files that have been generated,
> as long as they have not been updated by users. So I run
> TortoiseProc.exe /command:repostatus /path:[path] (aka "Check for
> modifications") But then I have to click "Check repository" to see
> what has been updated there, and filter through my "changes" that
> haven't been changed already in the repo (if they have I feel safe
> reverting those files).
>
> So it would be useful if you could run the "Check repository" right
> as you opened that window. Even better if you could tell the window
> what column to sort on.
Added param /remote in r16292.
Sorting the columns is not really suitable, since the user can rearrange
the columns and that new arrangement is remembered.
> Asking for external control over the view does not seems like an
> unusual UI scripting request, so I hope you'll take it under
> consideration.
For apps that don't have a command line client, sure, having scripting
ability over all UIs is good. But there already is a command line client
which provides everything you need to script commands for Subversion -
there's no need to provide our own scripting too. At least not for tasks
that don't require an UI (or users don't even want the UI).
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2016365
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-05-01 18:02:14 CEST