From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: Cygwin@Cygwin.Com
Subject: Installation data under "~/Downloads/cygwin/"
Date: Fri, 01 May 2015 11:35:00 -0000 [thread overview]
Message-ID: <21827.25837.938200.991974@woitok.gmail.com> (raw)
Cygwinners,
after installing and updating Cygwin for several times, my administrator
account's "~/Downloads/cygwin/" directory now amounts to roughly 6GB of
data, partially dating back to 2009. Is all this stuff still needed?
If not, what to keep? All the "*.ini" files? Or only the latest
"*.ini" file? Or what?
Sincerely
Rainer
--
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
next reply other threads:[~2015-05-01 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 11:35 Dr Rainer Woitok [this message]
2015-05-01 12:23 ` Marco Atzeri
2015-05-02 8:50 ` Andrey Repin
2015-05-04 17:58 ` Dr Rainer Woitok
2015-05-04 19:47 ` Warren Young
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=21827.25837.938200.991974@woitok.gmail.com \
--to=rainer.woitok@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).