1 patch for repository http://darcs.net/screened:

patch ad2a2b48618ccfdf78e41c6f8bbd1b754b9a6832
Author: Ben Franksen <ben.franksen@online.de>
Date:   Fri Nov 16 09:55:05 CET 2018
  * minimize context inside unrevert patch at the head of the unrevert bundle
  
  This does not minimize the context consisting of named patches in the bundle
  itself. Instead, only the prim patches that go inside the anonymous patch at
  the head of the unrevert bundle are affected.

Attachments

• minimize-context-inside-unrevert-patch-at-the-head-of-the-unrevert-bundle.dpatch
• patch-preview.txt
• unnamed

OK.

I had to think about this a bit to understand what's going on with
the unrevert patch. First the user splits unrecorded into 'norevert'
then 'p' (the stuff to be reverted). But the unrevert patch
needs to be relative to recorded, not unrecorded. So we need
to commute p with norevert, and if that fails then keep some
of norevert in the unrevert patch so it still makes sense. This
patch is about minimising how much of norevert we keep, rather than
the existing all/nothing decision.

> I had to think about this a bit to understand what's going on with
> the unrevert patch. First the user splits unrecorded into 'norevert'
> then 'p' (the stuff to be reverted). But the unrevert patch
> needs to be relative to recorded, not unrecorded. So we need
> to commute p with norevert, and if that fails then keep some
> of norevert in the unrevert patch so it still makes sense. This
> patch is about minimising how much of norevert we keep, rather than
> the existing all/nothing decision.

Exactly. It took me a while to figure that one out myself. Should put a
comment in the code, perhaps just copy and paste what you wrote above.

I added the comment in patch1822