IIRC these are pulled from branch-2.14.

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

patch 084e35c8083dc0fbbeb28c9a41f383c78c101a0d
Author: Ben Franksen <ben.franksen@online.de>
Date:   Tue Apr 28 16:22:42 CEST 2020
  * bump shelly version to 1.7.1.1 to avoid conflict with official version

patch 29bb91390b2b1d5066fc86d031b6f531a42e7275
Author: Ben Franksen <ben.franksen@online.de>
Date:   Wed Apr 29 11:49:34 CEST 2020
  * re-word the package description
  
  The motivation here was to explain better what makes Darcs different from
  other revision control systems. It is a bit more technical now and points
  out the conceptual simplicity that makes Darcs unique.

patch eb38e64eb542e475f64102a35acda3a94c16c5c5
Author: Ben Franksen <ben.franksen@online.de>
Date:   Wed Apr 29 12:27:43 CEST 2020
  * lots of updates to README.md
  
  This removes the link to http://darcs.net/Binaries, clarifies build
  instructions and documents limitations with respect to running the tests.
  The examples for running darcs have been reformatted and extended.
  Other sections have been partly re-worded and extended for clarity.

patch d09a942fd27365388bde0da8e1757eef3d9118c6
Author: Ben Franksen <ben.franksen@online.de>
Date:   Tue Apr 28 12:48:17 CEST 2020
  * add release notes for 2.14.4

patch e6c04d3fdf3fc5ee2ee083595ad213fcc2851dcd
Author: Ben Franksen <ben.franksen@online.de>
Date:   Thu Apr 30 13:34:11 CEST 2020
  * fix another instance where fail->error was wrong

Attachments

• bump-shelly-version-to-1_7_1_1-to-avoid-conflict-with-official-version.dpatch
• patch-preview.txt
• unnamed

On 20/06/2020 08:56, Ben Franksen wrote:

>   * bump shelly version to 1.7.1.1 to avoid conflict with official version

Fine.

>   * re-word the package description
>   
>   The motivation here was to explain better what makes Darcs different from
>   other revision control systems. It is a bit more technical now and points
>   out the conceptual simplicity that makes Darcs unique.

Thanks, I think the new one looks nice. (Slight nitpick would be whether
we can fairly claim that darcs is "unique" in being change-based, given
pijul, but I think it's reasonable enough.)

>   * lots of updates to README.md
>   
>   This removes the link to http://darcs.net/Binaries, clarifies build
>   instructions and documents limitations with respect to running the tests.
>   The examples for running darcs have been reformatted and extended.
>   Other sections have been partly re-worded and extended for clarity.

Another nice docs update, thanks!

>   * add release notes for 2.14.4

Fine.

>   * fix another instance where fail->error was wrong

Fine

>>   * re-word the package description
>>   
>>   The motivation here was to explain better what makes Darcs different from
>>   other revision control systems. It is a bit more technical now and points
>>   out the conceptual simplicity that makes Darcs unique.
> 
> Thanks, I think the new one looks nice. (Slight nitpick would be whether
> we can fairly claim that darcs is "unique" in being change-based, given
> pijul, but I think it's reasonable enough.)

This is a valid point. (If this were an abstract to a longer text I
would add a footnote here.)

Do you have an idea how to reformulate this so it does not make that
claim but is equally concise?

>> Thanks, I think the new one looks nice. (Slight nitpick would be whether
>> we can fairly claim that darcs is "unique" in being change-based, given
>> pijul, but I think it's reasonable enough.)
> 
> This is a valid point. (If this were an abstract to a longer text I
> would add a footnote here.)
> 
> Do you have an idea how to reformulate this so it does not make that
> claim but is equally concise?

It could use the word "special" or "different" instead of "unique", but
neither is perfect. A longer statement would be "different from most
revision control systems".

>> Do you have an idea how to reformulate this so it does not make that
>> claim but is equally concise?
> 
> It could use the word "special" or "different" instead of "unique", but
> neither is perfect. A longer statement would be "different from most
> revision control systems".

Okay, the slightly longer version is good, I think. See patch2069.

This consolidates my WIP patch with your "key instance" follow-up.

The second patch is something I needed to debug issue2727 but makes sense
independently IMO.

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

patch fd2fa87680ae5d6c78d50a495c8d671818606eb6
Author: Ben Franksen <ben.franksen@online.de>
Date:   Tue Jun  4 21:59:12 CEST 2024
  * add WithNames repo model wrapper for Named patches

  This is much cleaner than hacking the applied patch names into the existing
  repo models. Also led to a clean instance ArbitraryState (Named p) (which
  was buggy before) and may in the future allow to shrink Named patches by
  removing some of their explicit dependencies.

patch 10bfc319f392fdd2c29ae0d538463794e168c00c
Author: Ben Franksen <ben.franksen@online.de>
Date:   Tue Jun 11 13:28:17 CEST 2024
  * more useful instance Arbitrary PatchInfo for Named patches

  Shrinking patch names is problematic due to explicit dependencies and not
  needed if we generate only minimal, human readable (and always valid) names.

Attachments

• add-withnames-repo-model-wrapper-for-named-patches.dpatch
• patch-preview.txt

Last message send wrronewously to wrong patch. Please ignore.