2 patches for repository /home/ben/src/darcs/sent:

patch 709965fe05a51166c71bba0870c84a3a5de9eab5
Author: Ben Franksen <ben.franksen@online.de>
Date:   Mon Jun 17 15:15:25 CEST 2019
  * resolve issue2610: add --inherit-default option

patch 005ad8a944052a3b2ce4832298d81f624d63b114
Author: Ben Franksen <ben.franksen@online.de>
Date:   Mon Jun 17 13:57:29 CEST 2019
  * remove defunct --set-default option for rebase pull
  
  The option was never honored by this command.

Attachments

• patch-preview.txt
• resolve-issue2610_-add-__inherit_default-option.dpatch
• unnamed

Not screening this one immediately to give room for further design 
discussions. You may want to apply and look at the help output and/or 
the test script.

Note that there is currently the limitation that --inherit-default works 
only for local repositories (using isValidLocalPath). As explained in a 
comment in the code this is due to darcs/prefs/defaultrepo being treated 
as a text file, so we cannot reliably read it from a remote location 
(the URL/path may be encoded differently). I think this is okay for the 
intended use case (multiple local branches of a common upstream repo). 
Instead of treating it as a TODO comment I should document it in the 
help text. (I wrote that before I started to actually implement the 
feature).

Amended patch with improved help texts.

1 patch for repository /home/ben/src/darcs/sent:

patch d6decfee86649feea8be7503f7851fb461a97cf3
Author: Ben Franksen <ben.franksen@online.de>
Date:   Mon Jun 17 15:15:25 CEST 2019
  * resolve issue2610: add --inherit-default option

Attachments

• patch-preview.txt
• resolve-issue2610_-add-__inherit_default-option.dpatch
• unnamed

Updated bundle that includes a patch to further enhance security of the
feature.

2 patches for repository http://darcs.net/screened:

patch d6decfee86649feea8be7503f7851fb461a97cf3
Author: Ben Franksen <ben.franksen@online.de>
Date:   Mon Jun 17 15:15:25 CEST 2019
  * resolve issue2610: add --inherit-default option

patch ccaf002fd1ce38b981d55c08d1f0ce52364d1acb
Author: Ben Franksen <ben.franksen@online.de>
Date:   Tue Jun 18 23:27:34 CEST 2019
  * enhance security of --inherit-default
  
  We now check that the remote repo (dir) has the same owner as ".", reducing
  the danger of using a corrupt defaultrepo due to encoding mismatches between
  the remote and local repo.

Attachments

• patch-preview.txt
• resolve-issue2610_-add-__inherit_default-option.dpatch
• unnamed

> enhance security of --inherit-default

> hunk ./src/Darcs/Repository/Prefs.hs 502
[...]
> -- therefore encoded in the user's locale encoding. See issueXXXX 

issueXXXX should be updated :-)

To be honest I find the behaviour quite obscure/specialised, but I 
don't have any major objections if it makes a significant difference 
to your own workflows. I can't immediately think of anything cleaner 
that achieves the same goals.

Following up on review.

1 patch for repository http://darcs.net/screened:

patch 73d62183964597fa2d4a4c84541eca4bb53314b0
Author: Ben Franksen <ben.franksen@online.de>
Date:   Wed Aug 14 11:59:35 CEST 2019
  * fill in the placeholder "issueXXXX" with a proper reference

Attachments

• fill-in-the-placeholder-_issuexxxx_-with-a-proper-reference.dpatch
• patch-preview.txt
• unnamed

>> enhance security of --inherit-default
> 
>> hunk ./src/Darcs/Repository/Prefs.hs 502
> [...]
>> -- therefore encoded in the user's locale encoding. See issueXXXX 
> 
> issueXXXX should be updated :-)

Thanks for catching that one. I sent a patch that fills in the placeholder.

> To be honest I find the behaviour quite obscure/specialised, but I 
> don't have any major objections if it makes a significant difference 
> to your own workflows. I can't immediately think of anything cleaner 
> that achieves the same goals.

Adding in-repo branches could be a cleaner solution. The only problem
with such branches, if realised in the traditional way, is that we still
have only one working tree. This is often awkward, as switching between
branches then means we have to re-compile and cannot easily use external
tools to compare the branches. Perhaps, when we add branches to Darcs,
we should deviate from the traditional model and allow multiple working
trees for the different branches?

Anyway, for the moment I am satisfied with this work-around. We can
always delete it if we find a better solution.