From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Jeff King <peff@peff.net>
Cc: Chris Rorvick <chris@rorvick.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2012, #09; Mon, 29)
Date: Sat, 10 Nov 2012 18:33:38 +0000 [thread overview]
Message-ID: <509E9E02.3000500@ramsay1.demon.co.uk> (raw)
In-Reply-To: <20121104122926.GD336@sigill.intra.peff.net>
Jeff King wrote:
> On Fri, Nov 02, 2012 at 09:33:14PM +0000, Ramsay Jones wrote:
>
>> (Linux is my main platform, but I like to keep cygwin working because it has
>> kept me sane on Windows ever since (about) 1995 ...)
>> "Stranger in a strange land" ;-)
>
> I used a different trick around the same time to keep me sane from
> Windows, but I think it involved "dd" and "/dev/zero"...
;-) That's a solution I would have been keen to try, but my employer
at the time would not have liked that idea ...
>>
>> This patch fixes the test for me.
>
> Great. I was guessing blindly when I wrote it, but having seen the perl
> bug above, it all makes sense.
>
> We should probably wrap it. I'm planning to queue this on top of Chris's
> patch:
Unfortunately, I haven't had time yet to test this patch. (Early this week, I
went into hospital for a "minor" surgical procedure - I have not yet fully
recovered). The patch looks good and I don't anticipate any problems. I will
hopefully test it soon (I see it's in pu now) and let you know.
[snip patch]
ATB,
Ramsay Jones
next prev parent reply other threads:[~2012-11-10 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 10:21 What's cooking in git.git (Oct 2012, #09; Mon, 29) Jeff King
2012-11-01 18:40 ` Ramsay Jones
2012-11-02 1:12 ` Chris Rorvick
2012-11-02 9:43 ` Jeff King
2012-11-02 9:56 ` Jeff King
2012-11-02 21:33 ` Ramsay Jones
2012-11-04 12:29 ` Jeff King
2012-11-10 18:33 ` Ramsay Jones [this message]
2012-11-11 17:41 ` Jeff King
2012-11-13 18:47 ` Ramsay Jones
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=509E9E02.3000500@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=chris@rorvick.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).