[Monotone-commits-nodiffs] Revision 7b6b9a2e2e951d53d9af58899333aed011f966d1

[monotone]

-----------------------------------------------------------------
Revision: 7b6b9a2e2e951d53d9af58899333aed011f966d1
Ancestor: 33513953412998e03c1027d4e802fca6da9e9d1c
Author: Matthew Sackman <address@hidden>
Date: 2007-10-03T03:54:11
Branch: net.venge.monotone

Added files:
        contrib/monotone-mail-notify-standalone.sh
Modified files:
        contrib/monotone-mail-notify-standalone.lua

ChangeLog: 

Right, well, due to the continuously locked mtn db for servers, it makes
notification scripts a bit more complex. This change does roughly the
following:

1) The normal netsync hooks are used to construct files in _base. These
   specify where emails should be sent which has not changed (notify
   file in the confdir with the same structure as read_permissions).
2) Use cron or similar to call the .sh script. Make sure _base == $BASE
3) The .sh script reads the file and pulls from the server to a local
   db. This should be unused by everyone else. It then does mtn parents,
   mtn diff and uses source-highlight and mime-construct to build up one
   email per new revision which is properly mime structured. The
   resulting mime formatted mails have been testing in mutt,
   thunderbird/icedove and gnus. Finally, it sends the mail.


monotone --db={your.database} diff 
--revision=33513953412998e03c1027d4e802fca6da9e9d1c 
--revision=7b6b9a2e2e951d53d9af58899333aed011f966d1
----------------------------------------------------------------------