From: Chris Abbey <cabbey@bresnanlink.net>
To: <cygwin@cygwin.com>
Subject: Re: where to find nslookup for Cygwin?
Date: Sun, 17 Dec 2000 21:24:00 -0000 [thread overview]
Message-ID: <5.0.2.1.0.20001217230850.033bea20@pop.bresnanlink.net> (raw)
In-Reply-To: <3A3D2729.14763.151FF31@localhost>
At 20:50 12/17/00 -0800, Stephen C. Biggs wrote:
>Thank you for the reply. This does NOT entirely answer my question.
hmm... as has been pointed out, I didn't realize the difference
between preparing tarballs for the main distro and for the franken.de
server, those details will have to wait for someone more familiar
with the franken.de way of doing things to come on line. :( sorry.
> How can it be pre-patched and ALSO cygwin-specific??
in this case I'd interpret "pre-patched" as "previously patched",
not "before being patched". So the tarball is already containing
the cygwin specific code.
now the forces of openness
have a powerful and
unexpected new ally
http://ibm.com/linux/
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2000-12-17 21:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-17 11:57 Jari Aalto
2000-12-17 13:50 ` Corinna Vinschen
2000-12-17 14:52 ` Stephen C. Biggs
2000-12-17 15:13 ` Corinna Vinschen
2000-12-17 18:47 ` Stephen C. Biggs
2000-12-17 19:31 ` Chris Abbey
2000-12-17 20:44 ` Charles S. Wilson
2000-12-17 20:51 ` Stephen C. Biggs
2000-12-17 21:24 ` Chris Abbey [this message]
2000-12-18 0:44 ` Corinna Vinschen
2000-12-18 23:36 ` Stephen C. Biggs
2000-12-19 2:53 ` Corinna Vinschen
2000-12-19 3:24 ` Stephen C. Biggs
2000-12-19 4:07 ` Corinna Vinschen
2000-12-19 3:43 Pablo Ruiz Garcia
2000-12-19 4:23 ` Corinna Vinschen
2000-12-19 4:35 ` Gerrit P. Haase
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=5.0.2.1.0.20001217230850.033bea20@pop.bresnanlink.net \
--to=cabbey@bresnanlink.net \
--cc=cygwin@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).