Ian Jackson writes ("want split brain mode with --quilt={linear,...}"):
> I think all of --quilt={linear,auto,smash,nofix,nocheck} are
> potentially coherent in split brain mode.
FTR I am looking at this. Looking at the code structure I think some
reorganisation will be needed (and is a good idea anyway) and I want
to deal with this before introduce more quilt modes.
> Outstanding questions:
>
> * What should this thing be called in the documentation ?
> Currently we say "split view quilt mode" (see eg the docs
> for --save-dgit-view) but making it available more widely
> makes that wrong and it will also make it more visible.
>
> * Which of the following do we want:
> (i) --split-view={yes,auto,no} where
> dgit --split-view=no --quilt=dpm
> is an error
> (ii) --[no-]force-split-view with no way to force
> no split view
>
> * I guess split view should be controllable from a config
> option.
Opinions about these questions very welcome. I always find it
difficult to come up with good names and I sometimes have to change
the UI later due to making poor choices...
> * Does the existing machinery for quilt fixup implicitly assume
> non-split-brain, or is the implementation as simple as setting the
> split brain flag ?
The code for handling split brain quilt fixup is buried in the
multipatch quilt fixup routine. The current code structure in this
area is not very logical. I think some NFC shuffling about is needed,
at the very least.
Ian.
