On Tue, Nov 3, 2009 at 08:10, Dirk Illenberger <illenberger_at_niftybits.de>wrote:
> Suppose you have to commit a lot of changes which lead to transmission of a
> lot of data. Recently I had to commit 1.5 GB which took a few hours to
> finish. In the meantime I had to upload a couple of files to my web server.
> This couldn't wait and was urgent. So I had to make up my mind whether to
> cancel the commit (which had already run for 2 hours) or to allow for a
> longer upload time for the other files for the web server.
>
> If I had a pause button in the commit window this would solve my dilemma.
> It would pause committing after the file that is currently being processed.
> Then I would have uploaded the web server files and resumed committing
> afterwards.
>
> What do you think of that feature? I think it is pretty useful and easy to
> implement.
>
> Regards,
>
> Dirk.
>
That would have to be something that the server would allow, which as far as
I know a standard subversion server would not handle. I also don't know how
subversion handles multiple concurrent commits. However, a better suggestion
may be an option to turn on/off a bandwidth limitation from that dialog.
That would be something that would be client-side only and could be quite
useful. See "wget --limit-rate" for an example of what I mean.
Aaron
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2414110
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-11-03 14:23:06 CET