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

patch 03405cb927d9bb7d53097f80147bf60bdab5832d
Author: Ben Franksen <ben.franksen@online.de>
Date:   Tue Aug 20 12:34:15 CEST 2019
  * bump cabal version to 2.15.1

patch 486550da59dd836d385121ee29ded8ca174a5c05
Author: Ben Franksen <ben.franksen@online.de>
Date:   Tue Aug 20 12:34:59 CEST 2019
  tagged 2.15.1

Attachments

• bump-cabal-version-to-2_15_1.dpatch
• patch-preview.txt
• unnamed

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

patch 1b2fd6c7bcafd4859ccc468ba983b27349977221
Author: Ben Franksen <ben.franksen@online.de>
Date:   Tue Aug 20 12:36:30 CEST 2019
  * bump version to 2.15.1 in cabal file

patch f2956032391ddf319fffc8bb0f230c738bbd0282
Author: Ben Franksen <ben.franksen@online.de>
Date:   Tue Aug 20 12:36:54 CEST 2019
  tagged 2.15.1

Attachments

• bump-version-to-2_15_1-in-cabal-file.dpatch
• patch-preview.txt
• unnamed

Re-sending the bundle after we obliterated a patch it depends on.

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

patch 56b035e07c236b33a0502249e54fa3fb49db71ef
Author: Ben Franksen <ben.franksen@online.de>
Date:   Wed Aug 21 08:58:16 CEST 2019
  * bump version to 2.15.1 in cabal file

patch fc97160f4621fc3acd5e0ed6d35a7badea6164d8
Author: Ben Franksen <ben.franksen@online.de>
Date:   Wed Aug 21 08:59:08 CEST 2019
  tagged 2.15.1

Attachments

• bump-version-to-2_15_1-in-cabal-file.dpatch
• patch-preview.txt
• unnamed

Just a note for the future, next time let's tag the current state of
reviewed, not screened. Normally the version bump would be conflict-free 
with anything in flight so it shouldn't be a problem.

Having the tag in screened depending on patches under review means
that new patches being sent have the tag in their context so are a bit
more annoying to apply. And we don't get the performance benefits of
the tag when working on reviewed until it makes it there.

Also the tag will never denote a fully reviewed state of the repository,
because some submissions that get followups will end up split before and
after the tag.

> Just a note for the future, next time let's tag the current state of
> reviewed, not screened. Normally the version bump would be conflict-free 
> with anything in flight so it shouldn't be a problem.
> 
> Having the tag in screened depending on patches under review means
> that new patches being sent have the tag in their context so are a bit
> more annoying to apply. And we don't get the performance benefits of
> the tag when working on reviewed until it makes it there.
> 
> Also the tag will never denote a fully reviewed state of the repository,
> because some submissions that get followups will end up split before and
> after the tag.

100% agreed. I'll try to remember.