diff options
| author | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-03-19 19:55:37 +0000 |
|---|---|---|
| committer | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-03-19 19:55:37 +0000 |
| commit | b984d00921465ec778e59b750bc0e2366415e34c (patch) | |
| tree | b126bd9298726d69e359f8a0c42f9a8775ed3488 | |
| parent | 0416a79dfe63d1484fc08c29847f639e1970216c (diff) | |
another issue with the mercurual backend
| -rw-r--r-- | doc/todo/mercurial.mdwn | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/todo/mercurial.mdwn b/doc/todo/mercurial.mdwn index 0a20dd5b0..ff137a2e1 100644 --- a/doc/todo/mercurial.mdwn +++ b/doc/todo/mercurial.mdwn @@ -3,3 +3,10 @@ * Is the code sufficiently robust? It just warns when mercurial fails. * When rcs_commit is called with a $user that is an openid, it will be passed through to mercurial -u. Will mercurial choke on this? +* The rcs_commit implementation seems not to notice if the file has been + changed since a web edit started. Unlike all the other frontends, which + use the rcstoken to detect if the web commit started editing an earlier + version of the file, and if so, merge the two sets of changes together. + It seems that with the current mercurial commit code, it will always + blindly overwrite the current file with the web edited version, losing + any other changes. |