From: "Torsten Bögershausen" <tboegi@web.de>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: git@vger.kernel.org, kasal@ucw.cz
Subject: Re: [PATCH v2] blame: CRLF in the working tree and LF in the repo
Date: Thu, 30 Apr 2015 10:59:25 +0200 [thread overview]
Message-ID: <5541EEED.60004@web.de> (raw)
In-Reply-To: <83824ee9e8a2ea1e08b05aadbdd2d1b7@www.dscho.org>
On 30/04/15 09:53, Johannes Schindelin wrote:
> Hi Torsten,
>
> On 2015-04-30 06:42, Torsten Bögershausen wrote:
>> A typicall setup under Windows:
> s/ll/l/
>
>> What happened to the test cases ?
>> They where improved, but it turned out that they failed
>> from time to time, both Windows and Mac OS.
> Have you had a chance to investigate the failure symptoms? This is worrisome.
>
> Ciao,
> Dscho
Thanks for insisting - problem found:
< 00000000 (Not Committed Yet 2015-04-30 08:36:18 +0000 1) testcase
---
> 00000000 (Not Committed Yet 2015-04-30 08:36:19 +0000 1) testcase
(And V3 will come later)
prev parent reply other threads:[~2015-04-30 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 4:42 [PATCH v2] blame: CRLF in the working tree and LF in the repo Torsten Bögershausen
2015-04-30 7:53 ` Johannes Schindelin
2015-04-30 8:59 ` Torsten Bögershausen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5541EEED.60004@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=kasal@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).