From: Robert Collins <rbcollins@cygwin.com>
To: Charles Wilson <cwilson@ece.gatech.edu>
Cc: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: Re: [FAQ?] Re: [Mingw-users] Cygwin Full download in one big archive ?
Date: Thu, 05 Dec 2002 18:33:00 -0000 [thread overview]
Message-ID: <1039138394.13185.134.camel@lifelesswks> (raw)
In-Reply-To: <3DEFEAA3.30906@ece.gatech.edu>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
On Fri, 2002-12-06 at 11:09, Charles Wilson wrote:
> Sortof. I assumed <i>a priori</i> that a 557MB tarball is a bad idea.
Yep. And the original poster, was asserting that such a tarball is a
good idea. Thus my figures to show that it ain't - for the common case.
> I was not, in any way, suggesting that setup learn how to parse a cygwin
> "installation" created by some moron unzipping a bunch of tarballs by
> hand. No way. Never.
Whew :}. I didn't think *you* would suggest such a thing. I was more
worried about having the last word, so that the archives will show it to
be a bad thing :}.
Rob
--
---
GPG key available at: http://users.bigpond.net.au/robertc/keys.txt.
---
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2002-12-06 1:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 6:46 Richard Campbell
2002-12-05 6:57 ` Max Bowsher
2002-12-05 8:18 ` Brian Gallew
2002-12-05 9:20 ` news
[not found] ` <200212051653.gB5GrrP09822@mx1.redhat.com>
2002-12-05 14:18 ` [Mingw-users] cygwin " Christopher Faylor
2002-12-05 14:20 ` [Mingw-users] Cygwin " Robert Collins
2002-12-05 15:39 ` [FAQ?] " Charles Wilson
2002-12-05 15:55 ` Robert Collins
2002-12-05 16:32 ` Charles Wilson
2002-12-05 18:33 ` Robert Collins [this message]
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=1039138394.13185.134.camel@lifelesswks \
--to=rbcollins@cygwin.com \
--cc=cwilson@ece.gatech.edu \
--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).