From: Patrick Ohly <patrick.ohly@intel.com>
To: Randy Witt <rewitt@declaratino.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] rm_work_and_downloads.bbclass: more aggressively minimize disk usage
Date: Sat, 07 Jan 2017 09:09:58 +0100 [thread overview]
Message-ID: <1483776598.4383.24.camel@intel.com> (raw)
In-Reply-To: <CAP5N7XH56aXsVvqVns=Pa4mbmHOZvGecD638nApM94LHibpDqQ@mail.gmail.com>
On Fri, 2017-01-06 at 13:29 -0800, Randy Witt wrote:
> There are times that the work directories help with the debugging of
> build failures. The logs aren't always enough. So a person might want
> to do something like remove the downloads, but preserve the actual
> work, especially in the case of failures.
>
>
> I'll admit it is a fabricated scenario, but in general I'm against one
> knob requiring the turning of another knob.
In principle I agree. Okay, let's separate the two.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-01-07 8:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 9:55 [PATCH 0/3] rm_work enhancements Patrick Ohly
2017-01-06 9:55 ` [PATCH 1/3] gcc-source.inc: cleanly disable do_rm_work Patrick Ohly
2017-01-09 18:47 ` Khem Raj
2017-01-06 9:55 ` [PATCH 2/3] rm_work_and_downloads.bbclass: more aggressively minimize disk usage Patrick Ohly
2017-01-06 18:31 ` Randy Witt
2017-01-06 19:22 ` Patrick Ohly
2017-01-06 21:29 ` Randy Witt
2017-01-07 8:09 ` Patrick Ohly [this message]
2017-01-09 10:25 ` Patrick Ohly
2017-01-09 18:17 ` Randy Witt
2017-01-06 9:55 ` [PATCH 3/3] rm_work.bbclass: clean up sooner Patrick Ohly
2017-02-15 18:32 ` Martin Jansa
2017-02-16 10:26 ` Patrick Ohly
2017-03-01 15:52 ` Martin Jansa
2017-03-01 16:44 ` Patrick Ohly
2017-03-01 18:47 ` Martin Jansa
2017-03-02 10:13 ` Patrick Ohly
2017-03-02 9:38 ` Patrick Ohly
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=1483776598.4383.24.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rewitt@declaratino.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