urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

web commit by http://ethan.betacantrips.com/

master
joey 2007-01-14 08:16:09 +00:00
parent 559344048c
commit c87c7edf28
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/patchqueue/move_page.mdwn
View File

@ -26,6 +26,21 @@ Anyhow, here's the patch, for whatever good it does.
> implement a move operation -- falling back to an add and delete. > implement a move operation -- falling back to an add and delete.
> --[[Joey]] > --[[Joey]]
Hmm. Shouldn't that be done on a by-RCS basis, though? (i.e. implemented
by backends in the `rcs_move` function)
Also, how should ikiwiki react if a page is edited (say, by another user)
before it is moved? Bail, or shrug and proceed?
Could you elaborate on [[commit-internals]]? Can I assume that ikiwiki's
working copy W will always reflect a revision of the master copy M?
(That is, nobody changes W and leaves it uncommitted.) I would guess
probably not; a user probably expects that if he starts editing W it
won't get randomly committed by web user actions. But then looking at
the svn backend, it looks like if I edit foo.mdwn, don't commit, and then
a web user makes different changes, my changes get wiped out. So does
W "belong" to ikiwiki? --Ethan
diff -urx .svn ikiwiki/IkiWiki/CGI.pm ikiwiki-new/IkiWiki/CGI.pm diff -urx .svn ikiwiki/IkiWiki/CGI.pm ikiwiki-new/IkiWiki/CGI.pm
--- ikiwiki/IkiWiki/CGI.pm 2007-01-04 03:52:47.000000000 -0800 --- ikiwiki/IkiWiki/CGI.pm 2007-01-04 03:52:47.000000000 -0800