public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: DJ Delorie <dj@delorie.com>
To: DMcCunney@roper.com
Cc: cygwin@sourceware.cygnus.com
Subject: Re: A new user of cygwin and unix based system
Date: Mon, 28 Jun 1999 09:18:00 -0000	[thread overview]
Message-ID: <199906281617.MAA15020@envy.delorie.com> (raw)
In-Reply-To: <65CAA822B707D211AD430008C7F40FED1F8553@EXCHANGERSW2>

> If I might make a couple of suggestions:

Suggestions are always welcome!

> First, you might wish to post a mini-FAQ here on a regular basis.

Hmmm... I already post a djgpp mini-faq; I suppose I could do a cygwin
mini-faq also.

> I got the impression from reading your posts here that you were officially
> involved with Cygwin, for instance, but this is the first post of yours
> signed with your title that I recall seeing.

For the record, Chris is the manager of the cygwin group, and I'm the
only engineer in the group (my official title is "senior engineer").
Chris also manages another group in Cygnus, so I'm the only true
full-time employee on cygwin.  Our responsibilities include not only
cygwin development, but also supporting development by other groups on
the windows platform and doing other windows-related internal
projects.  I'm also working on our next "GNUPro" release.

> (I found out about this mailing list from a FAQ included with a cygwin
> distribution, but the address given for subscribing to the list was _wrong_,
> and bounced with an "unknown recipient" error.  I got pointed in the right
> direction by a chap on the NTEmacs mailing list.)

That would be the old gnu-win32@cygnus.com address, which I thought
would bounce with a *useful* message.

> Second, please consider adding either a stand-alone info reader or a groff
> port to the distribution.

I have those on my machine.  Porting was actually pretty easy; you
might try it yourself as an exercise.  Texinfo just needed a makefile
tweak (add .exe to makedoc), GNU groff built without changes, and you
can get "man" sources from any linux distribution - no changes needed
there either.  Our goal (well, mine at least) is to make cygwin
compatible enough that "./configure; make; make install" works just as
often (and as well) as on Unix.  In this case, it almost does.

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

WARNING: multiple messages have this Message-ID
From: DJ Delorie <dj@delorie.com>
To: DMcCunney@roper.com
Cc: cygwin@sourceware.cygnus.com
Subject: Re: A new user of cygwin and unix based system
Date: Wed, 30 Jun 1999 22:10:00 -0000	[thread overview]
Message-ID: <199906281617.MAA15020@envy.delorie.com> (raw)
Message-ID: <19990630221000.-egz9bNdSALS41q99gGwFyRK1mXSi91OcGIyze4Vj58@z> (raw)
In-Reply-To: <65CAA822B707D211AD430008C7F40FED1F8553@EXCHANGERSW2>

> If I might make a couple of suggestions:

Suggestions are always welcome!

> First, you might wish to post a mini-FAQ here on a regular basis.

Hmmm... I already post a djgpp mini-faq; I suppose I could do a cygwin
mini-faq also.

> I got the impression from reading your posts here that you were officially
> involved with Cygwin, for instance, but this is the first post of yours
> signed with your title that I recall seeing.

For the record, Chris is the manager of the cygwin group, and I'm the
only engineer in the group (my official title is "senior engineer").
Chris also manages another group in Cygnus, so I'm the only true
full-time employee on cygwin.  Our responsibilities include not only
cygwin development, but also supporting development by other groups on
the windows platform and doing other windows-related internal
projects.  I'm also working on our next "GNUPro" release.

> (I found out about this mailing list from a FAQ included with a cygwin
> distribution, but the address given for subscribing to the list was _wrong_,
> and bounced with an "unknown recipient" error.  I got pointed in the right
> direction by a chap on the NTEmacs mailing list.)

That would be the old gnu-win32@cygnus.com address, which I thought
would bounce with a *useful* message.

> Second, please consider adding either a stand-alone info reader or a groff
> port to the distribution.

I have those on my machine.  Porting was actually pretty easy; you
might try it yourself as an exercise.  Texinfo just needed a makefile
tweak (add .exe to makedoc), GNU groff built without changes, and you
can get "man" sources from any linux distribution - no changes needed
there either.  Our goal (well, mine at least) is to make cygwin
compatible enough that "./configure; make; make install" works just as
often (and as well) as on Unix.  In this case, it almost does.

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

  reply	other threads:[~1999-06-28  9:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-28  8:38 McCunney, Dennis
1999-06-28  9:18 ` DJ Delorie [this message]
1999-06-29  4:16   ` install.exe (Was: A new user of cygwin and unix based system) David Starks-Browning
1999-06-30 22:10     ` David Starks-Browning
1999-06-30 22:10   ` A new user of cygwin and unix based system DJ Delorie
1999-06-28 18:11 ` 'Chris Faylor'
1999-06-29  7:50   ` Chris Faylor
1999-06-30 22:10     ` Chris Faylor
1999-06-30 22:10   ` 'Chris Faylor'
1999-07-04 15:59   ` Michael Hirmke
1999-07-04 19:06     ` Chris Faylor
1999-07-31 18:34       ` Chris Faylor
1999-07-31 18:34     ` Michael Hirmke
1999-07-05 16:12   ` Michael Hirmke
1999-07-31 18:34     ` Michael Hirmke
1999-06-30 22:10 ` McCunney, Dennis
     [not found] <no.id>
1999-07-01 23:09 ` Glenn Spell
1999-07-02  9:06   ` Chris Faylor
1999-07-31 18:34     ` Chris Faylor
1999-07-31 18:34   ` Glenn Spell
1999-07-02  9:45 ` Glenn Spell
1999-07-31 18:34   ` Glenn Spell
  -- strict thread matches above, loose matches on Subject: below --
1999-06-26 16:48 Jons
1999-06-26 18:35 ` Chris Faylor
1999-06-30 22:10   ` Chris Faylor
1999-06-30 22:10 ` Jons

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=199906281617.MAA15020@envy.delorie.com \
    --to=dj@delorie.com \
    --cc=DMcCunney@roper.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).