X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/b551c0604e46f66d83b9db18b6e6e8b518f93d99..cf1290eb464f1256aa5c12d973fff774e4f83e5e:/doc/todo/option_to_send_only_the_diff_in_notifyemail.mdwn

diff --git a/doc/todo/option_to_send_only_the_diff_in_notifyemail.mdwn b/doc/todo/option_to_send_only_the_diff_in_notifyemail.mdwn
index 42b0d1ca6..b863d361d 100644
--- a/doc/todo/option_to_send_only_the_diff_in_notifyemail.mdwn
+++ b/doc/todo/option_to_send_only_the_diff_in_notifyemail.mdwn
@@ -1,5 +1,11 @@
 [[!tag wishlist]]
 
+[[!template  id=gitbranch branch=anarcat/notifychanges author="[[anarcat]]"]]
+
 It would be nice if [[plugins/notifyemail]] wouldn't send the complete page source, but only the things that changed, when notifying users. They can always follow the link to see the full page if they want.
 
 For bonus points, make that optional. --[[anarcat]]
+
+> I am working on a patch, in the branch mentionned above. So far, my first job was to make sure notifyemail sends a single email per refresh. Next step is to try to figure out the revisions to send to the user - I am not sure it's quite obvious in the iki internals which diffs we're working on, because of the pluggable nature of the software (and even the possibility that not RCS exists at all). So far, I am thinking of using `rcs_recentchanges()`, but how many commits to look back into? Feedback welcome. --[[anarcat]]
+
+> > It turns out it was easier to simply make a completely new plugin for this, which I called "notifychanges" (i don't like that name too much). It is in my notifychanges branch, so i guess we have a [[!taglink patch]] now! --[[anarcat]]