Bug Tracker Home
Lost your login?
Created on 2018-10-06.21:36:08 by bfrk, last changed 2020-08-01.09:52:01 by bfrk.
This should not need any further explanation. The current behavior is
that we get no warning and no markup. Completely unacceptable IMO.
Author: Ben Franksen <email@example.com>
Date: Wed Nov 14 22:00:30 CET 2018
* resolve issue2603: warn and mark conflicts when cloning