From: Jon Turney <jon.turney@dronecode.org.uk>
To: "Frank Ch. Eigler" <fche@redhat.com>, overseers@sourceware.org
Subject: Re: mystery disk usage growth spurts
Date: Sun, 06 Mar 2016 15:37:00 -0000 [thread overview]
Message-ID: <56DC4EA6.1060304@dronecode.org.uk> (raw)
In-Reply-To: <20160305220239.GA6322@redhat.com>
On 05/03/2016 22:02, Frank Ch. Eigler wrote:
> Hi -
>
> cgf wrote:
>
>> How about ~cygwin ?
>> % du -s ~cygwin | comma
>> 243,951,236 /sourceware/cygwin-staging
>
> Excellent guess:
>
> % du -s /sourceware*/cygwin-staging/jturney/*/*
> 80170548 /sourceware1/cygwin-staging/jturney/backup/20160211121400
> 80817956 /sourceware1/cygwin-staging/jturney/backup/20160219132504
> 82844828 /sourceware1/cygwin-staging/jturney/backup/20160301182520
>
> Jon, please clean up & take steps to prevent such a buildup. Thanks!
I've removed these.
prev parent reply other threads:[~2016-03-06 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 16:48 Frank Ch. Eigler
2016-03-05 17:16 ` Gerald Pfeifer
2016-03-05 17:41 ` Christopher Faylor
2016-03-05 22:02 ` Frank Ch. Eigler
2016-03-06 15:37 ` Jon Turney [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=56DC4EA6.1060304@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=fche@redhat.com \
--cc=overseers@sourceware.org \
/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).