From: Adrian Cox <adrian@humboldt.co.uk>
To: cygwin@cygwin.com
Subject: Re: How do I get an old version of cygwin?
Date: Thu, 20 Jan 2005 10:08:00 -0000 [thread overview]
Message-ID: <1106214469.7522.54.camel@localhost> (raw)
In-Reply-To: <20050119180645.GA2624@efn.org>
On Wed, 2005-01-19 at 10:06 -0800, Yitzchak Scott-Thoennes wrote:
> Gets kind of old to hear this "debated" over and over again when it's
> clear that the developers are not interested in the work involved.
>
> Time for a cygwin-multi-versions (moderated?) list? cygwin-licensing
> was very successful at reducing the licensing traffic (both here and
> there).
It would be useful if there was a forum for people who distribute
cygwin1.dll along with an application. I'm not very interested in the
whole Cygwin distribution, and I'm going to end up maintaining an
in-house fork of the code to solve my problems. I doubt I'm the only one
doing this, and I'll happily take it to a more appropriate list.
I'm even prepared to host the list myself if there's demand. If anybody
else does need to do this sort of thing, mail me off list.
--
Adrian Cox <adrian@humboldt.co.uk>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2005-01-20 9:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 23:20 James M. Rogers
2005-01-18 1:02 ` Larry Hall
2005-01-18 16:25 ` Doctor Bill
2005-01-18 16:25 ` Christopher Faylor
2005-01-18 9:34 ` Adrian Cox
2005-01-18 14:53 ` Christopher Faylor
2005-01-19 16:18 ` Adrian Cox
2005-01-19 16:46 ` Christopher Faylor
2005-01-19 18:18 ` Yitzchak Scott-Thoennes
2005-01-20 10:08 ` Adrian Cox [this message]
2005-01-20 11:43 ` Corinna Vinschen
2005-01-21 10:47 ` Adrian Cox
2005-01-20 13:02 ` Dave Korn
2005-01-20 19:04 ` Christopher Faylor
2005-01-21 16:27 ` Christopher Faylor
2005-01-19 0:09 Steve Munson
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=1106214469.7522.54.camel@localhost \
--to=adrian@humboldt.co.uk \
--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).