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

responses

master
Joey Hess 2010-05-12 15:42:28 -04:00
parent 7112da3ed1
commit 3f2f447cb5
2 changed files with 29 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/forum/debian_backports_update_someone_please.mdwn
View File

@ -5,3 +5,8 @@ I'm just in the process of deploying ikiwiki and I'd love to use it in the html5
> for 2 weeks. :) --[[Joey]] > for 2 weeks. :) --[[Joey]]
>> And are there any chances you doing it... or rather not doing it? >> And are there any chances you doing it... or rather not doing it?
>>> Sure, I'm busily not doing it right now. Should reach testing in 3
>>> days. I generally schedule things so a new ikiwiki reaches testing
>>> every 2 weeks to month. Getting important new features and bugfixes out
>>> can take priority though. --[[Joey]]

24
doc/forum/how_do_I_revert_edits_in_the_web_mode__63__.mdwn
View File

@ -3,3 +3,27 @@ Puzzled a bit :-/
> There is no explicit interface for reverting edits. Most of us use `git revert`. --[[Joey]] > There is no explicit interface for reverting edits. Most of us use `git revert`. --[[Joey]]
>> That's a blow; I was planning on appointing no techies to keep law and order on our pages :-/ Is there a plugin or at least a plan to add such a 'in demand' feature? >> That's a blow; I was planning on appointing no techies to keep law and order on our pages :-/ Is there a plugin or at least a plan to add such a 'in demand' feature?
>>> A lot of things complicate adding that feature to the web interface.
>>>
>>> First, ikiwiki happily uses whatever the VCS's best of breed web
>>> history interface is. (ie, viewvcs, gitweb). To allow reverting
>>> past the bottom of the RecentChanges page, it would need to have its
>>> own history browser. Not sure I want to go there.
>>>
>>> And the mechanics of handling reverting can quickly get complex.
>>> Web reverting should only allow users to revert things they can edit,
>>> but reverting a whole commit in git might touch multiple files.
>>> Some files may not be editable over the web at all. (The
>>> [[tips/untrusted_git_push]] also has to deal with those issues.)
>>> Finally, a revert can fail with a conflict. The revert could touch
>>> multiple files, and multiple ones could conflict. The conflict may
>>> involve non-page files that can't be diffed. So an interface for
>>> resolving such a conflict could be hard.
>>>
>>> Probably web-based reverting would need to be limited to reverting
>>> single file changes, not whole commits, and not having very good
>>> conflict handling. And maybe only being accessible for changes
>>> still visible on RecentChanges. With those limitations, it's certianly
>>> doable (as a plugin even), but given how excellent `git revert` is in
>>> comparison, I have not had a real desire to do so. --[[Joey]]