It took me a while to figure out that --look-for-adds plus --summary
(whether implied or not) is the one special case for whatsnew, everything
else can be handled generically using allInterestingChanges. The code should
make this clear(er) now.

3 patches for repository http://darcs.net/screened:

patch 169d542a3b91ee01447590f447219cd31032156c
Author: Ben Franksen <ben.franksen@online.de>
Date:   Thu Apr 20 08:14:05 CEST 2017
  * whatsnew: fixed wrong use of term hunk in help texts and comments

patch bb0f962634b0dc75c99e4b9e36fa97ebdf613f06
Author: Ben Franksen <ben.franksen@online.de>
Date:   Thu Apr 20 10:44:13 CEST 2017
  * whatsnew: minor cleanups (fix duplicate import, comments, indentation)

patch 47d44607a14efc3cb4ebe397f2a41c1b1ca70fe2
Author: Ben Franksen <ben.franksen@online.de>
Date:   Thu Apr 20 11:17:33 CEST 2017
  * fix whatsnew -l --no-summary

Attachments

• patch-preview.txt
• unnamed
• whatsnew_-fixed-wrong-use-of-term-hunk-in-help-texts-and-comments.dpatch

This bundle has 1 patch in reviewed and 2 in screened. Why have you
marked it as obsoleted?

Frankly, I can't remember exactly, this has been several months ago.
When I mark a bundle obsolete I usually have a good reason, so I guess
you can simply ignore this one.

Code looks correc and tests passes; accepted.