DarcsWatch can be found at http://darcswatch.nomeata.de/.
DarcsWatch is a tool to track the state of darcs patches that have been submitted to some project, usually by using the darcs send command. It allows both submitters and project maintainers to get an overview of patches that have been submitted but not yet applied. Some notable features are:
You can check the DarcsWatch website for new, unapplied patches to your favorite projects and directly download them to try them out.
The easiest way to apply a patch from DarcsWatch is to copy the URL from the download link and paste it into a terminal, to run this command: GET http://darcswatch.nomeata.de/...dpatch | darcs apply -i
To have your patch submissions tracked, you have to send them to firstname.lastname@example.org. The easiest way to achieve this is by adding the line send cc email@example.com to ~/.darcs/defaults.
If the repositories you are submitting to are not yet tracked, you have to drop a note to Joachim Breitner with the repository URL, and it will be added.
If you receive patches on a mailing list and want to have them tracked by DarcsWatch, just subscribe firstname.lastname@example.org to the list, and drop Joachim Breitner a note with the darcs repository URL.
If you receive patches directly, but want them tracked by DarcsWatch, you should set up an email address somewhere that forwards all mails to both yourself and email@example.com. If you can not do that. get in touch with Joachim Breitner, he might be able to set something up for you.
If a patch is submitted to the Darcs project, a ticket in their roundup instance is created. DarcsWatch notices this and links the entries both ways. When DarcsWatch detects that the patch bundle is completely appiled in a repository, it will close the ticket as “accepted”.
Not much. Patch bundles are stored by their MD5 sum, so if the same hash bundle arrives again, it will just override the old one.
Yes, but only for whole patch bundles. There are two ways, the latter just for reference, as the first one is easier:
Via tagged mails DarcsWatch remembers the message-ids of the mails that submitted a particular patch bundle, so if it sees a direct reply to such a mail, it looks in the subject for the text [OBSOLETE] or [REJECTED] and marks a patch as such. If the bundle (or parts of it) are later re-submitted, these flags are removed again.
If you don’t have the original message around to reply to it, you can also attach the patch bundle to the mail with the tag in the subject – just download it from the DarcsWatch site. Also, when patch bundles are added to DarcsWatch manually, there might not be a message-id attached and this will be the only way.
Via inverse patches. Make sure DarcsWatch has seen the inverse of the patch. You can do so by first running darcs rollback and select your patch, and then send it to DarcsWatch using darcs send --firstname.lastname@example.org. If the project is using a mailing list that is being tracked by DarcsWatch, you can send this mail to the list, thus notifying your fellow developers that you consider your patch obsolete. Of course you can do this also to patches other than your own.
Via updated patches. Additionally, if the same author submits a patch with the same name and description as a previous patch, but with a later date, DarcsWatch assumes that darcs amend-record was used and that the earlier patch is obsolete.
You can find DarcsWatch’s own darcs repository on http://darcs.nomeata.de/darcswatch.
darcswatch © Joachim Breitner <email@example.com>