From: Harald Seiler <hws@denx.de>
To: isar-users@googlegroups.com
Subject: [PATCH 0/2] Clean bitbake.conf and allow DL_DIR from env
Date: Tue, 27 Nov 2018 10:52:14 +0100 [thread overview]
Message-ID: <840a2535ca72f3ff2c900b2ce111fa9f60c1ee84.camel@denx.de> (raw)
As suggested by Jan in <09b4d369-b3bf-0e2e-7d1e-47b1660d555e@siemens.com>:
> Then I would say - in order to keep bitbake/ clean - we should promote
> isar-bitbake.conf to the only bitbake.conf we use, migrating current
> bitbake.conf content over.
Harald Seiler (2):
meta: Only use isar's own bitbake.conf
meta: Allow setting DL_DIR from environment
meta/conf/isar-bitbake.conf | 30 +++++++++++++++++++++++++++++-
scripts/isar-setup-builddir | 21 ---------------------
2 files changed, 29 insertions(+), 22 deletions(-)
--
Harald
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-62 Fax: +49-8142-66989-80 Email: hws@denx.de
next reply other threads:[~2018-11-27 9:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 9:52 Harald Seiler [this message]
2018-11-27 9:53 ` [PATCH 1/2] meta: Only use isar's own bitbake.conf Harald Seiler
2018-12-07 14:30 ` Jan Kiszka
2018-12-10 9:31 ` Claudius Heine
2018-12-10 9:32 ` Jan Kiszka
2018-11-27 9:54 ` [PATCH 2/2] meta: Allow setting DL_DIR from environment Harald Seiler
2018-12-10 10:22 ` [PATCH v2 0/3] Clean bitbake.conf and allow DL_DIR from env claudius.heine.ext
2018-12-10 10:22 ` [PATCH v2 1/3] meta: Only use isar's own bitbake.conf claudius.heine.ext
2018-12-10 10:25 ` Harald Seiler
2018-12-10 10:22 ` [PATCH v2 2/3] meta: Allow setting DL_DIR from environment claudius.heine.ext
2018-12-10 10:22 ` [PATCH v2 3/3] meta: rename isar-bitbake.conf to bitbake.conf claudius.heine.ext
2018-12-10 12:05 ` [PATCH v2 0/3] Clean bitbake.conf and allow DL_DIR from env Maxim Yu. Osipov
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=840a2535ca72f3ff2c900b2ce111fa9f60c1ee84.camel@denx.de \
--to=hws@denx.de \
--cc=isar-users@googlegroups.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