From: Michael Halstead <mhalstead@linuxfoundation.org>
To: Changqing Li <changqing.li@windriver.com>,
akuster808 <akuster808@gmail.com>, Khem Raj <raj.khem@gmail.com>,
openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Shall we remove bad-checksum files on http://sources.openembedded.org/?
Date: Wed, 12 Dec 2018 10:32:51 -0800 [thread overview]
Message-ID: <3045fc0b-288e-322f-e4eb-d6ff637abf2f@linuxfoundation.org> (raw)
With the current setup files will accumulate on
http://sources.openembedded.org/ over time and none will be removed. Are
there any patterns that should be removed over time? *bad-checksum*
files seem like an obvious choice. Please share concerns or suggust
other patterns to remove.
Thank you,
--
Michael Halstead
Linux Foundation / SysAdmin
next reply other threads:[~2018-12-12 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 18:32 Michael Halstead [this message]
2018-12-12 18:48 ` Shall we remove bad-checksum files on http://sources.openembedded.org/? Khem Raj
2018-12-12 21:18 ` Michael Halstead
2018-12-12 22:07 ` Khem Raj
2018-12-12 23:40 ` Philip Balister
2018-12-13 0:57 ` Khem Raj
2018-12-13 16:08 ` Philip Balister
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=3045fc0b-288e-322f-e4eb-d6ff637abf2f@linuxfoundation.org \
--to=mhalstead@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=changqing.li@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.