diff options
author | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-08-21 04:25:03 +0000 |
---|---|---|
committer | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-08-21 04:25:03 +0000 |
commit | 74baaeba00c90cd7a027e40e2f6d65695341a0e1 (patch) | |
tree | 6439c954ca575ce40bb965745d4cb67bec8f329e /doc/subversion | |
parent | 764d91b6befacfca98676519b90a0c257d17f177 (diff) |
reorg all the pages about rcs backends. Fix all links
Diffstat (limited to 'doc/subversion')
-rw-r--r-- | doc/subversion/discussion.mdwn | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/doc/subversion/discussion.mdwn b/doc/subversion/discussion.mdwn deleted file mode 100644 index 426735182..000000000 --- a/doc/subversion/discussion.mdwn +++ /dev/null @@ -1,13 +0,0 @@ -If the user interrupts the page loading during the running of `svn commit`, -the repository will be left in an inconsistent state. The probability of -this happening increases with the size of the repository and the number of -plugins installed, because these both affect how long the post-commit hook -takes to run. (The core issue, I guess, is that we're abusing the concept -of a "working copy" by giving everybody the same one). Here are the main -solutions that I can see: (1) CGI queues commits so that a single process -can act upon them sequentially, or (2) optionally divorce the `ikiwiki ---refresh` from the `svn commit` so that commits happen faster. -- [[Ben]] - -I'm not aware of web servers, at least apache, killing cgi processes when -the user stops a page load. If this is happening ikiwiki should be able to -avoid it by blocking whatever signal is causing it to terminate. --[[Joey]] |