summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-01-17 02:32:48 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-01-17 02:32:48 +0000
commit6c0e2d92879598cb3dac890247119b0672899b51 (patch)
tree5fd5d662af0bea31f00660ef25a16b8862b04d4c /doc
parentb6537c8a16687ebb58d79ceaff5cfc5ecedf6742 (diff)
web commit by http://ethan.betacantrips.com/: more info
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/svn_fails_to_update.mdwn8
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/bugs/svn_fails_to_update.mdwn b/doc/bugs/svn_fails_to_update.mdwn
index fda003a44..015ab5a2b 100644
--- a/doc/bugs/svn_fails_to_update.mdwn
+++ b/doc/bugs/svn_fails_to_update.mdwn
@@ -70,4 +70,10 @@ To be honest I don't know what will happen in this case (svn merge fails?
conflict markers?), but I'm pretty sure it's a problem. Anyhow, I think we
should call update manually after commit, I just don't know if this should
be RCS-specific, or whether it's safe to update after commit on all RCSes.
---Ethan \ No newline at end of file
+--Ethan
+
+Hmm, turns out that isn't the case! svn's prepedit function calls svn info
+which gets the "right" information even when the WC isn't current. I am
+having problems merging but that probably has nothing to do with this bug.
+[This patch](http://ikidev.betacantrips.com/patches/update.patch) calls
+rcs_update after commit in CGI.pm, it might be a good idea anyhow. --Ethan \ No newline at end of file