diff options
| author | www-data <www-data@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2006-03-19 19:27:59 +0000 |
|---|---|---|
| committer | www-data <www-data@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2006-03-19 19:27:59 +0000 |
| commit | 52db4a50f6423eba6d513f6a3e1ec246c14aa9de (patch) | |
| tree | d0a58b7a9ca0705f8eb4ac3d7db3cac7a18400c9 | |
| parent | 53146f395cf979f93b9d53607d71993d1fbc7fed (diff) | |
web commit by joey
| -rw-r--r-- | doc/todo.mdwn | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/todo.mdwn b/doc/todo.mdwn index b6c38036d..71c0eb972 100644 --- a/doc/todo.mdwn +++ b/doc/todo.mdwn @@ -16,6 +16,8 @@ Well, it could keep track of the version number of the page it started editing, and if it's changed during the edit, ask svn to merge all changes from that version number to head into the page after writing it out. Doing that without races with other svn committers seems tricky. + If each commit operated in a separate copy of the wc, that was created for the commit, the steps above would work. But it would be very expensive to make and maintain all those copies. + Note that unless we use `svn lock`, we really can't "warn" about concurrent edits and such the way other wikis do, which is ok, since that system sucks anyway. Using svn up for smart merging will be much nicer most of the time. * Eventually, might want page deletion. |