public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Package file lists archive
Date: Wed, 18 Jun 2014 06:53:00 -0000	[thread overview]
Message-ID: <CAAXzdLVAp_rKLNravSrH81-Kx12TXq2VwwWNcDdxRQxe7Eoc8Q@mail.gmail.com> (raw)
In-Reply-To: <20140618061812.GE4920@ednor.casa.cgf.cx>

On Wed, Jun 18, 2014 at 1:18 AM, Christopher Faylor wrote:
> Your idea of "constructive" is apparently flawed.

This is an interesting comment, taking in that your response ignores the
original question and focuses on off topic quibbling. I will pose your viewpoint
and my question again

> And, frankly, I think it's a bad idea to keep a monolithic list of
> packages available for people to download anyway.

Do you have an explanation for this opinion, or citations as to why this is a
bad idea, taking into account that major Linux distros are already using this
very method?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2014-06-18  6:53 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26  5:01 Steven Penny
2014-05-26 21:22 ` Christopher Faylor
2014-05-27  9:46   ` Steven Penny
2014-05-27 22:17     ` Christopher Faylor
2014-06-09 10:45       ` Steven Penny
2014-06-12  3:13         ` Steven Penny
2014-06-12 15:44           ` PolarStorm
2014-06-09 15:17       ` Warren Young
2014-06-09 16:17         ` Steven Penny
2014-06-17 14:29           ` Christopher Faylor
2014-06-18  4:29             ` Steven Penny
2014-06-18  6:18               ` Christopher Faylor
2014-06-18  6:53                 ` Steven Penny [this message]
2014-06-18 12:29                   ` Larry Hall (Cygwin)
2014-06-18 14:24                     ` Steven Penny
2014-06-18 15:23                       ` Christopher Faylor
2014-08-03 21:07                         ` Steven Penny
2014-08-04  3:01                           ` Yaakov Selkowitz
2014-08-04  3:38                             ` Steven Penny
2014-08-07 17:38                               ` Steven Penny
2014-08-07 17:49                                 ` Larry Hall (Cygwin)
2014-08-07 21:04                                   ` Steven Penny
2014-08-07 21:42                                     ` Larry Hall (Cygwin)
2014-08-08  1:05                                       ` Andrey Repin
2014-08-08  1:30                                         ` Steven Penny
2014-08-08  2:05                                           ` Andrey Repin
2014-08-08  2:13                                             ` Steven Penny
2014-08-08  3:21                                               ` Steven Penny
2014-08-08  3:33                                           ` Yaakov Selkowitz
2014-08-08  3:59                                             ` Steven Penny
2014-08-08  4:55                                               ` Yaakov Selkowitz
2014-06-18 15:22                   ` Christopher Faylor
2014-06-12 21:58   ` Steven Penny
2014-06-17 14:27     ` Christopher Faylor

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=CAAXzdLVAp_rKLNravSrH81-Kx12TXq2VwwWNcDdxRQxe7Eoc8Q@mail.gmail.com \
    --to=svnpenn@gmail.com \
    --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).