> I guess either return all the raw unravelled conflicts and let the
> caller handle mangling what it can and reporting on the rest, or return
> the mangled ones + the raw unravelled ones we can't mangle.
The latter, then. Here we go.
BTW, only the last patch is new, the rest is dependencies.
3 patches for repository http://darcs.net/screened:
patch 6b11cedb1dde629063fc9b21894246734427c67c
Author: Ben Franksen <ben.franksen@online.de>
Date: Tue Jul 16 21:34:44 CEST 2019
* resolve issue2550: apply only properly mangled resolutions, warn about any others
To support this change we add the new data type StandardResolution and
return that from standardResolution. It contains a summary of the data we
gathered from calling resolveConflicts: the mangled resolutions, merged into
a single FL, the list of conflicted paths, and an IO action to warn about
and display any (unravelled) conflicts that we couldn't properly mangle. The
warning is normally only displayed if we actually want mangling to happen
i.e. if --mark-conflicts is in effect (except for the mark-conflicts command).
patch b57365b1d1990d5493086608ef466841e81c4b8f
Author: Ben Franksen <ben.franksen@online.de>
Date: Tue Jul 16 21:46:45 CEST 2019
* move announceConflicts from D.R.Merge to D.R.Resolution
patch 09bbd7ae6fe2ae2cee8a2e64ce975438a02d1bdd
Author: Ben Franksen <ben.franksen@online.de>
Date: Fri Aug 9 01:04:08 CEST 2019
* store the raw unmangled parts of a conflict in StandardResolution
This allows client code to display them in any form they wish, not
necessarily using ePutDocLn. We do provide warnUnmangled as a convenience
function, but also showUnmangled and even more low-level showUnravelled.
Attachments
|