This is the mail archive of the
mailing list for the Cygwin project.
Re: Will next cygwin1.dll release have the select() fix?
On Sat, 15 Nov 2003 Brian.Kelly@Empireblue.com wrote:
> My hearty congratulations to Mr. Ford.
> I'm sure it will look good on his resume.
> >>> *I was actually given Brian Ford*
> I thought slavery in this country ended with the Civil War, or is Mr. Ford
> a form of *artificial intelligence*?
Yeah, that's it! I'm just a robot creation of Chris'. That happens
automatically when you start hacking on Cygwin code, like Chris said.
> Anyhow - how much do you want for him/it?
Sorry, not for sale.
In all fairness, I did answer your question, all be it in a somewhat
sarcastic manner. Reread the quote below.
I'm sure it was not really deserving of a gold star. So, I'll gladly
relinquish it if it'll make you feel better.
Brian Ford wrote:
> On Fri, 14 Nov 2003 Brian.Kelly@Empireblue.com wrote:
>> Chris Faylor wrote:
>>> I'm wondering what you think the term "snapshot" means.
>> cvs - as opposed to setup.exe
>What do you think the cvs repository is for?
>> So I take it I'm wrong and can get the select() fix via default setup.exe?
>Not now, but the next release will be based off cvs. Doh!
>That is what snapshots are for, to test for a yet to be determined
>>> Standard flip answer: Definitely by December 2004.
>> Is there such a thing as a standard "non-flip" answer?
> Cygwin is a voluteer effort. Releases do not happen on a schedule.
> Volunteer yourself, or take what you get.
Anyway, can we *please* just drop this noise now.
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html