Re: [PATCH] Move path_prefix_p declaration from cygheap.h to path.h

[Christopher Faylor <cgf at redhat dot com>]

On Mon, Oct 15, 2001 at 10:09:55PM -0500, Gary R. Van Sickle wrote:
>> Ok.  Lets just stop the discussion right here.
>>
>> I will deal with the issue of header file inclusion.
>>
>> I'm not asking for a discussion of everyone's idea of the best way to
>> handle things.  I don't want to go down that rat hole.
>
>Mr.  Faylor, I apologize if I have, in some manner which escapes me,
>offended you or anyone else involved in the Cygwin project, a project
>which I find inestimably valuable both personally and to the computing
>community as a whole.  I was merely attempting to volunteer my services
>to abate deficiencies we both saw in the project.

I'm not offended! I appreciate what you're trying to do.  I probably
should have said that before.  I just don't want to have a header file
discussion.  I've had way too many header file discussions in my life.

I'm aware of all of the pros and cons of the various ways of handling
things and I'll eventually do something about it.

IMO, the only way to handle this type of situation is to have one person
make the decision.  That would be me.  And, I *will* eventually get
to this issue.

Gary, if you are looking for a contribution to the the project that would
make a lot of difference to a lot of people, then the documentation is
in real need of work.  People keep sticking their heads up to volunteer
and then disappearing.

For a programming task, ensuring that setup.exe is in a solid state for
use with the new category/dependency stuff would both be immensely
valuable.

Another thing that I've mentioned in the past is rationalizing the
option handling of all of the utilities in winsup/utils.  I'd like
everything to use getopt_long eventually.

Or, maybe Robert would like some input on his cygwin/daemon code.

The time/timezone handling is in need of some inspection.  We should come
up with a way to transition to the linux-way of handling timezones without
breaking legacy cygwin apps.

If you are looking for a contribution to the project that would make a
lot of difference to *me*, then either keeping an eye out on the cygwin
mailing list for bugs that need fixing and getting up to speed on fixing
them would be great.  Even some of the bugs reported in cygwin-developers
are "I don't have time to fix this" variety.

(Btw, if you want to join cygwin-developers, I'll approve you)

I very much don't want this to be one of those "Well, *I* tried to help
with Cygwin development and Chris shot me down"
cygwin-mailing-list-true-life-confesssions.  I appreciate that you're
trying to help.  That is extremely rare in cygwin-land.

cgf