It has always bugged me that we have so many modules named ApplyPatches.
This refactor at least removes the one under Darcs.Apply; the functionality
is now part of Darcs.Repository.ApplyPatches, its only consumer.
3 patches for repository http://darcs.net/screened:
patch 4634fe991652152c99fda9b9dc4da29615bb3bad
Author: Ben Franksen <ben.franksen@online.de>
Date: Thu Nov 5 10:40:20 CET 2020
* minor refactor in D.UI.ApplyPatches
patch a80ed9a6f564c45183c0c407f04de01d45e742e7
Author: Ben Franksen <ben.franksen@online.de>
Date: Tue Nov 24 09:20:29 CET 2020
* remove Darcs.Patch.ApplyPatches
patch e9447ae22c0c8ac14886c1cdc46173508db88f8d
Author: Ben Franksen <ben.franksen@online.de>
Date: Tue Nov 24 09:26:21 CET 2020
* cleanup import lists in Darcs.Repository.ApplyPatches
All fine. I think I introduced the modules to separate the
UI/Repository/Patch layers, but D.P.ApplyPatches is
clearly a bit small to be worthy of its own module.
History
Date
User
Action
Args
2020-12-21 16:30:47
bfrk
create
2020-12-21 16:31:41
bfrk
set
status: needs-screening -> needs-review title: minor refactor in D.UI.ApplyPatches (and 2 more) -> remove Darcs.Patch.ApplyPatches (and 2 more)