From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: claudius.heine.ext@siemens.com, isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH] remove TODO file, items if still applicable, should be on gh tracker
Date: Thu, 28 Mar 2019 15:42:04 +0100 [thread overview]
Message-ID: <dd6e8c54-de84-2cb1-1be3-70751c13a5c5@ilbers.de> (raw)
In-Reply-To: <20190328130406.26929-1-claudius.heine.ext@siemens.com>
On 3/28/19 2:04 PM, claudius.heine.ext@siemens.com wrote:
> From: Claudius Heine <ch@denx.de>
Applied to the 'next'. Applicable items were created on isar's github
tracker.
Thanks,
Maxim.
> Signed-off-by: Claudius Heine <ch@denx.de>
> ---
> TODO | 28 ----------------------------
> 1 file changed, 28 deletions(-)
> delete mode 100644 TODO
>
> diff --git a/TODO b/TODO
> deleted file mode 100644
> index b71bf51..0000000
> --- a/TODO
> +++ /dev/null
> @@ -1,28 +0,0 @@
> -* Way to manage dependencies for multi-devroot.
> -
> -* Get rid of sudo.
> -
> -* Bitbake parallel jobs vs. DEB_BUILD_OPTIONS=parallel=n.
> -
> -* Add option to build package from source or to pull binary deb from apt
> - (BUILD_FROM_SRC, bump pkg ver).
> -
> -* Add basic OE classes for fetch, unpack etc.
> -
> -* Integrate Debian package building.
> -
> -* Create apt repos?
> -
> -* Dependency mgmt (debian vs. bitbake dependencies).
> -
> -* Bitbake: If a lib has changed, an app using it won't be rebuilt.
> -
> -* Repo or git subproject... for the right bitbake version?
> -
> -* Kconfig.
> -
> -* Optional cross-building support (performance?).
> -
> -* Override Debian repo with a local one.
> -
> -* runqemu.
>
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
prev parent reply other threads:[~2019-03-28 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 13:04 claudius.heine.ext
2019-03-28 14:42 ` Maxim Yu. Osipov [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=dd6e8c54-de84-2cb1-1be3-70751c13a5c5@ilbers.de \
--to=mosipov@ilbers.de \
--cc=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--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