From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: "Bad address" error with redirection (stdout and stderr) in background process
Date: Mon, 16 Jan 2012 19:13:00 -0000 [thread overview]
Message-ID: <20120116191337.GB23201@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4F1436D2.20702@gmail.com>
On Mon, Jan 16, 2012 at 02:40:18PM +0000, Dave Korn wrote:
>On 16/01/2012 06:47, Heiko Elger wrote:
>> Dave Korn gmail.com> writes:
>>
>>> looks like there was a second snapshot later the same day that replaced the
>>> one you had installed.
>>
>> That's it! Thanks a lot ..
>> I never see a snapshot released twice a day ....
>>
>> Just one question:
>> How can I figure out whether a snapshot is released more than once a day?
>
> Well, if ...
>
>- you download a snapshot
>- you find a bug
>- you report it and discuss it on the list
>- cgf says he's just created a snapshot to fix your bug
>
>... you can infer by pure logic alone that he's not talking about the
>snapshot that was uploaded *before* you reported your bug.
Thank you Dave, for a good thirty seconds of LOL.
cgf
parent reply other threads:[~2012-01-16 19:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4F1436D2.20702@gmail.com>]
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=20120116191337.GB23201@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).