Dirk Illenberger 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.
Subversion commits are atomic. That was in fact the main reason
Subversion was started, because CVS didn't have that very, very
Atomic commits means that a commit either succeeds or fails, no matter
how many files are committed.
Now imagine if there was a 'pause' button: while your commit is paused,
you would block all other commits to those same files. And that's
something that would never, ever get implemented in Subversion.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-11-03 19:14:42 CET