public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@cygnus.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: Cygwin B20 - fseek under gcc fails to reposition on text files
Date: Fri, 19 Feb 1999 17:21:00 -0000	[thread overview]
Message-ID: <19990219202153.A32178@cygnus.com> (raw)
In-Reply-To: < 8525671D.00525F37.00@D51MTA10.pok.ibm.com >; from setera@us.ibm.com on Fri, Feb 19, 1999 at 09:00:04AM -0600

On Fri, Feb 19, 1999 at 09:00:04AM -0600, setera@us.ibm.com wrote:
>
>>Currently, Corinna, Mumit, and a couple of other people are the only
>>outside contributers to the project.  Everyone else seems to be in
>>"Cygwin doesn't work the way I think it should when I run program X.
>>Here's the error message." mode.
>>
>>I'm collecting the error messages and hope to investigate problems but
>>the reality is that this is a volunteer effort for DJ and me.  Our
>>real jobs don't offer much time for tracking down net problems.
>
>I can certainly understand your frustrations.  In my GIMP work, I've had a
>heck of a time with some hanging problems which I've reported to you.  I
>report them to you and DJ not because I *expect* you to jump and fix them,
>but because I am clueless on how to fix them myself.  I *have* downloaded
>the source code and *have* attempted to understand the infrastructure
>enough to solve the problems.  In my case at least, if there were more
>documentation on the internals of the winsup code, I might be able to solve
>some problems on my own.  Unfortunately, I think with the exception of a
>few people (you, DJ, Sergey, etc) most do not have a good enough
>understanding of the internals of winsup to really be able to help out.  On
>the other hand, I try not to complain about things either.

It is not impossible to figure out how things work with cygwin.  I know
because I did it.  You may not remember, or maybe you weren't around,
but I started out as a net contributer before Cygnus hired me.

Cygwin is certainly considerably less complicated than Linux ever was
and people have managed to make considerable contributions to the Linux
kernel.

As I said, if you can't contribute, I certainly understand but, it's a fact of
life that things are not going to change quickly with 2.5 people working on the
project, especially when most of those people have day jobs.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

WARNING: multiple messages have this Message-ID
From: Christopher Faylor <cgf@cygnus.com>
To: cygwin@sourceware.cygnus.com
Subject: Re: Cygwin B20 - fseek under gcc fails to reposition on text files
Date: Sun, 28 Feb 1999 23:02:00 -0000	[thread overview]
Message-ID: <19990219202153.A32178@cygnus.com> (raw)
Message-ID: <19990228230200.aWsIfClVTx2ykYrPJZj4qEzsXmDTugN2dzkRq8WRbKw@z> (raw)
In-Reply-To: <8525671D.00525F37.00@D51MTA10.pok.ibm.com>

On Fri, Feb 19, 1999 at 09:00:04AM -0600, setera@us.ibm.com wrote:
>
>>Currently, Corinna, Mumit, and a couple of other people are the only
>>outside contributers to the project.  Everyone else seems to be in
>>"Cygwin doesn't work the way I think it should when I run program X.
>>Here's the error message." mode.
>>
>>I'm collecting the error messages and hope to investigate problems but
>>the reality is that this is a volunteer effort for DJ and me.  Our
>>real jobs don't offer much time for tracking down net problems.
>
>I can certainly understand your frustrations.  In my GIMP work, I've had a
>heck of a time with some hanging problems which I've reported to you.  I
>report them to you and DJ not because I *expect* you to jump and fix them,
>but because I am clueless on how to fix them myself.  I *have* downloaded
>the source code and *have* attempted to understand the infrastructure
>enough to solve the problems.  In my case at least, if there were more
>documentation on the internals of the winsup code, I might be able to solve
>some problems on my own.  Unfortunately, I think with the exception of a
>few people (you, DJ, Sergey, etc) most do not have a good enough
>understanding of the internals of winsup to really be able to help out.  On
>the other hand, I try not to complain about things either.

It is not impossible to figure out how things work with cygwin.  I know
because I did it.  You may not remember, or maybe you weren't around,
but I started out as a net contributer before Cygnus hired me.

Cygwin is certainly considerably less complicated than Linux ever was
and people have managed to make considerable contributions to the Linux
kernel.

As I said, if you can't contribute, I certainly understand but, it's a fact of
life that things are not going to change quickly with 2.5 people working on the
project, especially when most of those people have day jobs.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


  parent reply	other threads:[~1999-02-19 17:21 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-19  7:00 setera
     [not found] ` < 8525671D.00525F37.00@D51MTA10.pok.ibm.com >
1999-02-19 17:21   ` Christopher Faylor [this message]
1999-02-22 13:40     ` Corinna Vinschen
1999-02-28 23:02       ` Corinna Vinschen
1999-02-28 23:02     ` Christopher Faylor
1999-02-28 23:02 ` setera
  -- strict thread matches above, loose matches on Subject: below --
1999-02-22 14:28 Earnie Boyd
1999-02-28 23:02 ` Earnie Boyd
1999-02-16  7:41 Earnie Boyd
     [not found] ` < 19990216154134.3413.rocketmail@send104.yahoomail.com >
1999-02-16 17:52   ` Christopher Faylor
     [not found]     ` < 19990216205243.L16511@cygnus.com >
1999-02-16 18:18       ` DJ Delorie
1999-02-28 23:02         ` DJ Delorie
1999-02-17  2:01     ` Corinna Vinschen
     [not found]       ` < 36CA92B5.844635AA@cityweb.de >
1999-02-17  8:07         ` DJ Delorie
1999-02-28 23:02           ` DJ Delorie
1999-02-17 13:46         ` J. J. Farrell
1999-02-28 23:02           ` J. J. Farrell
1999-02-17  9:36       ` Re[2]: " Paul Sokolovsky
     [not found]         ` < 17817.990217@is.lg.ua >
1999-02-17 10:07           ` DJ Delorie
     [not found]             ` < 199902171807.NAA16764@envy.delorie.com >
1999-02-17 19:16               ` Larry Hall
     [not found]                 ` < 3.0.5.32.19990217221306.0162b070@pop.ma.ultranet.com >
1999-02-17 19:19                   ` DJ Delorie
     [not found]                     ` < 199902180318.WAA20394@envy.delorie.com >
1999-02-17 20:13                       ` Larry Hall
1999-02-28 23:02                         ` Larry Hall
1999-02-28 23:02                     ` DJ Delorie
1999-02-28 23:02                 ` Larry Hall
1999-02-28 23:02             ` DJ Delorie
1999-02-17 13:37         ` Corinna Vinschen
1999-02-19  2:30           ` Re[2]: " Paul Sokolovsky
     [not found]             ` < 17776.990218@is.lg.ua >
1999-02-19  6:36               ` Christopher Faylor
1999-02-28 23:02                 ` Christopher Faylor
1999-02-28 23:02           ` Corinna Vinschen
1999-02-28 23:02       ` Corinna Vinschen
1999-02-28 23:02     ` Christopher Faylor
1999-02-28 23:02 ` Earnie Boyd
1999-02-16  5:27 Earnie Boyd
1999-02-28 23:02 ` Earnie Boyd
1999-02-16  4:24 Peter Kabal
1999-02-28 23:02 ` Peter Kabal

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=19990219202153.A32178@cygnus.com \
    --to=cgf@cygnus.com \
    --cc=cygwin@sourceware.cygnus.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).