Am 04.07.20 um 23:59 schrieb James Cook:
>> I think that whenever a sequence of patches starts and ends at a
>> primitive context (e.g. this is true of an unconflicted repository)
>> you can re-order the patches so that they are all primitive.
>
> I should add: this probably requires allowing new
Am 04.07.20 um 23:43 schrieb James Cook:
> On Sat, 4 Jul 2020 at 09:59, Ben Franksen wrote:
>> Am 04.07.20 um 00:10 schrieb James Cook:
> I'd say this is a feature, not a bug. If you mark the conflict between A
> and B as resolved, *without* recording a new patch, then this means you
Hi darcs-users,
I'm trying to learn more about how darcs force commutes work.
What I'd like to do is create a repository R1 with patches A and B,
and then look at the patches that result if A and B get
force-commuted.
E.g. if I could pull just patch B and not A to a new repository, I
think that
