From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: snapshots revisited
Date: Fri, 11 Mar 2011 16:44:00 -0000 [thread overview]
Message-ID: <20110311164438.GA22554@ednor.casa.cgf.cx> (raw)
In-Reply-To: <AANLkTim+WXCg-ddYHw1DXu-NTkDs0n121gkPzpBU7Uzk@mail.gmail.com>
On Fri, Mar 11, 2011 at 04:17:55PM +0000, Andy Koppe wrote:
>Please let the matter rest now and go back to testing snapshots.
Actually, not to be technical in cygwin-talk but the last problem I
found with the pipe code is, so-far, a show-stopper. This is, I think,
the first time I've seen a Windows function somewhat succeed but still
return an error code. I don't know how to deal with that yet.
cgf
next prev parent reply other threads:[~2011-03-11 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110310080923.19244yp07upxphcz@messagerie.si.c-s.fr>
[not found] ` <20110310091353.GU12899@calimero.vinschen.de>
[not found] ` <20110310232423.GA3588@ednor.casa.cgf.cx>
[not found] ` <20110310232514.GA10198@ednor.casa.cgf.cx>
[not found] ` <20110311082012.GE7064@calimero.vinschen.de>
[not found] ` <20110311152511.GB4645@ednor.casa.cgf.cx>
[not found] ` <COL102-W10B426004D410A3549CE47B5CB0@phx.gbl>
2011-03-11 15:58 ` Christopher Faylor
2011-03-11 16:13 ` David Eisner
2011-03-11 16:18 ` Andy Koppe
2011-03-11 16:44 ` Christopher Faylor [this message]
2011-03-12 4:27 ` Buchbinder, Barry (NIH/NIAID) [E]
2011-03-12 17:16 ` Lee D. Rothstein
2011-03-12 17:41 ` Corinna Vinschen
2011-03-12 18:21 ` Christopher Faylor
2011-03-12 18:39 ` Corinna Vinschen
2011-03-12 18:55 ` Christopher Faylor
2011-03-12 19:53 ` Corinna Vinschen
2011-03-12 19:54 ` Buchbinder, Barry (NIH/NIAID) [E]
2011-03-12 20:10 ` Corinna Vinschen
2011-03-12 21:11 ` Christopher Faylor
2011-03-12 21:32 ` Corinna Vinschen
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=20110311164438.GA22554@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin-talk@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).