Hi Eric and Reiner,
new text within comment looks good and thanks for issue1937 (Isn't
that Matthias's comment?).
Is it possible to host the picture files on some Darcs related server?
Next are some status updates not directly related to this email.
I look looked shortly on delta debugging method  but I'm not sure
If I understood from the code what it is doing. Without the code I
would assume that no other method is possible except brute-force for
searching smallest possible set of the patches which makes the test
succeeded (e.g. all combination). Of course in the case of the Darcs
we have defined starting point and space is reduced by patch
dependencies. Is that assumption correct?
I'm still trying to finish correction for that but I'm not able to
concentrate on that enough. I started writing a new version of the
configuration description  for both Windows and Linux for the
OpenSSH and the PuTTY (standard cases) with internal support within
Darcs for ssh suite auto-detection. In addition there will be
description how to configure the any other SSH suite by additional
configuration. The coding part itself should not be hard for me to
On Mon, Aug 30, 2010 at 2:58 PM, Eric Kow <firstname.lastname@example.org> wrote:
> Hi Rado and Reinier,
> 1 patch for repository http://darcs.net/releases/branch-2.5:
> Rado: I noticed there were some FIXMEs in the user manual, which I assume
> are yours/Matthias's. I tried to write some basic documentation for trackdown
> following your guide (now moved to http://wiki.darcs.net/Using/Trackdown ).
> I've also created issue1937 for your second FIXME.
> Mon Aug 30 13:55:30 BST 2010 Eric Kow <email@example.com>
> * Clean up trackdown --bisect documentation.
> This email has been scanned by MessageLabs' Email Security
> System on behalf of the University of Brighton.
> For more information see http://www.brighton.ac.uk/is/spam/
Whoops, this is one case where our BTS infrastructure does the wrong
thing, by not recognising replies generated when people who are CC'ed by
the patch submitter reply to all.
I've attached Rado's message to the correct patch375