public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Keith Christian <keith1christian@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Future of 32-bit distro (was: rebase-4.4.3-1 regression: Too many DLLs for available address space)
Date: Fri, 12 Jan 2018 22:00:00 -0000	[thread overview]
Message-ID: <CAFWoy7E8VAPUBDm--pNCbiFCj_ed+OgXsHyQtdqmBRJ7oZ3LnQ@mail.gmail.com> (raw)
In-Reply-To: <0DB190A7-5951-42D4-9EA9-A37E807EEC29@solidrocksystems.com>

See my post in the other "Re: Future of 32-bit distro" thread about
using setup-x86.exe to remove KDE and GNOME.

Keith

--
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:[~2018-01-12 22:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-11 12:31 rebase-4.4.3-1 regression: Too many DLLs for available address space Christian Franke
2018-01-11 16:06 ` Corinna Vinschen
2018-01-11 17:53   ` Achim Gratz
2018-01-11 17:56   ` Corinna Vinschen
2018-01-11 21:52 ` Denis Excoffier
2018-01-12  9:13   ` Corinna Vinschen
2018-01-12 18:11     ` Future of 32-bit distro (was: rebase-4.4.3-1 regression: Too many DLLs for available address space) Yaakov Selkowitz
2018-01-12 19:02       ` Future of 32-bit distro Brian Inglis
2018-01-12 19:33         ` Keith Christian
     [not found]           ` <7218003ac95dc6814bbb309dda3df748@smtp-cloud8.xs4all.net>
2018-01-13  1:56             ` Brian Inglis
2018-01-13  2:15               ` Keith Christian
2018-01-12 19:40         ` Steven Penny
2018-01-12 20:20       ` Future of 32-bit distro (was: rebase-4.4.3-1 regression: Too many DLLs for available address space) Vince Rice
2018-01-12 22:00         ` Keith Christian [this message]
2018-01-13  9:11       ` Future of 32-bit distro David Stacey
2018-01-12 17:16 ` rebase-4.4.3-1 regression: Too many DLLs for available address space Thomas Waldmann

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=CAFWoy7E8VAPUBDm--pNCbiFCj_ed+OgXsHyQtdqmBRJ7oZ3LnQ@mail.gmail.com \
    --to=keith1christian@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).