fb6074c48a2cf6234>
2. As for Darcsden, the backend of <http://hub.darcs.net>, progress has been
made on modernizing the ssh server used by it:
- <https://hub.darcs.net/ganesh/ssh/issue/5>
- <https://hub.darcs.net/simon/darcsden>
# Issues resolved (7)
i
this working we could take our current workflow from
bugs.darc.net to hub.darcs.net
* I manually rebased this patch at https://hub.darcs.net/gh/darcsden/
, waiting for someone to review it. :-)
Guillaume
2017-07-31 15:26 GMT-03:00 Guillaume Hoffmann <guilla...@gmail.com>:
> Hi,
>
> yest
Hi all,
there has been a recent breakage of darcs 2.12 build on stackage, and
fixing it would require bumping several dependencies upper bounds,
including base.
Rather than doing that, I find more economical to prepare a release of
Darcs 2.14. For this we need to fix the following:
* windows
detect conflicts
> but it never did, and it took years for anyone to notice, so it seems
> not so critical. Once the regression is fixed then there original
> patch can be amended with a performance fix at leisure.
>
> On Tue, Dec 12, 2017 at 4:00 PM, Guillaume Hoffmann <guilla..
GMT-03:00 Ben Franksen <ben.frank...@online.de>:
> Am 11.12.2017 um 15:34 schrieb Guillaume Hoffmann:
>> Hi all,
>>
>> there has been a recent breakage of darcs 2.12 build on stackage, and
>> fixing it would require bumping several dependencies upper bounds,
>
Interface ##
- fix encoding business, make DARCS_DONT_ESCAPE_8BIT=1 default (Ben
Franksen, Ganesh Sittampalam)
- show explicit dependencies in `darcs log -s` (Gian Piero Carrubba)
- improve bash/zsh completion (Ben, Gian Piero)
- no longer print an error message when ctrlc'ing pager (Guillaume Hoffmann
>> That would be great.
>
> I have fixed them both, ha!
Great!
> Okay, sounds good. I will be away from home for a week or so, but I hope
> I will have WiFi. If not, or it's unreliable or low bandwidth: I have
> uploaded all pending patches that I intended for screened but haven't
> sent yet to
8-02-07 20:22 GMT-03:00 Guillaume Hoffmann <guilla...@gmail.com>:
> Hi Jens,
>
> Sorry for the delay!
>
> In the coming days I am going to create the 2.14 branch, review the
> patches that are currently on the bug tracker and see if we can make a
> 2.14.0 release.
>
&g
