summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-01-15 18:58:04 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-01-15 18:58:04 +0000
commita0f714b20a0ac86b083097c470f4cb982427f707 (patch)
tree321b4d893ff56f482d18842f7e8d7c4e99e9cc95
parent2aaba01a7ae73431e99bb59280b663e1a30a2447 (diff)
web commit by http://ethan.betacantrips.com/: more thoughts
-rw-r--r--doc/bugs/svn_fails_to_update.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/bugs/svn_fails_to_update.mdwn b/doc/bugs/svn_fails_to_update.mdwn
index 6f2c9fd31..eebace453 100644
--- a/doc/bugs/svn_fails_to_update.mdwn
+++ b/doc/bugs/svn_fails_to_update.mdwn
@@ -40,3 +40,11 @@ but *does* happen when committing from the web.
> Yeah, this makes sense now that you bring it up. Perhaps I should make
> ikiwiki skip the update when called from the post-commit hook if the repo
> is locked, although this could mask other problems.. --[[Joey]]
+
+>> I don't think it's (yet) a serious problem, because any commit to the repo
+>> either comes from another WC, in which case, no problem, or it is committed by
+>> ikiwiki through its own WC, in which case that WC is "the newest". The only problem
+>> is that ikiwiki's rcs information for web commits gets screwed up. I think the
+>> correct fix is to call rcs_update from rcs_commit in svn.pm, if
+>> the commit succeeds. I'm not sure whether this ought to happen for all RCSes
+>> or just svn. --Ethan \ No newline at end of file