[darcs-users] so long and thanks for all the darcs

Karl O. Pinc kop at meme.com
Mon Mar 5 00:47:43 UTC 2018


On Sun, 4 Mar 2018 23:23:33 +0100
Ben Franksen <ben.franksen at online.de> wrote:

> What made me re-consider
> the idea was that I found I like the way mercurial automatically
> creates a branch when you pull a conflicting patch.

> But
> when you look at it from a darcs viewpoint, automatically creating a
> branch really makes sense only if there is no "clean" merge, that is
> if there is a conflict; otherwise you just pull patches and that's it.

FYI.  I regularly pull with --no-allow-conflicts.

> In any case
> you'd rather want to avoid doing conflict resolution when you are in
> the middle of finishing something else.

Agreed.

> In contrast, branches are fully symmetric: none is better
> than the other, patch identities remain unmodified, and you can
> switch between them easily.

Would be nice to be able to assume that the remote repo 
is not "better".

> 
> Branches would also allow us to do many of the "destructive"
> operations less dangerously by default.

Does sound appealing.

> These are all pretty raw ideas at the moment, none of it is
> implemented. There are lots of open questions regarding UI design etc.

I know a lot of thought gets done on IRC but as far as UI
goes it might be good to run thoughts by this mailing list.

Up to you.

Regards, and thanks for all the work!

Karl <kop at meme.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein


More information about the darcs-users mailing list