From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "Hombourger, Cedric" <Cedric_Hombourger@mentor.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH 0/1] Remove hard-code distro name in the multistrap template
Date: Wed, 21 Feb 2018 17:10:01 +0100 [thread overview]
Message-ID: <d0e7c3c7-3e1e-215d-4d00-c02209ddd103@siemens.com> (raw)
In-Reply-To: <d8930961f09f4a39bdedabf09f0be078@svr-ies-mbx-02.mgc.mentorg.com>
Hi Cedric,
On 02/21/2018 04:51 PM, Hombourger, Cedric wrote:
> Awesome :)
>
> If I am not mistaken, there are still some TODOs for the multistrap removal patch series
> (it however does look very promising!). If I may offer my opinion, I would suggest we get this small patch integrated (if acceptable ofcourse!)
Yeah of course.
My message wasn't really addressed for you specifically or a statement
against merging of your patch. I wrote it because your patch touches the
same code basis as mine and this bug could have been carried into my
implementation with debootstrap.
Cheers,
Claudius
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de
next prev parent reply other threads:[~2018-02-21 16:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 13:19 Cedric Hombourger
2018-02-21 13:19 ` [PATCH 1/1] buildchroot: remove hard-coded distro names " Cedric Hombourger
2019-02-22 10:26 ` Henning Schild
2019-02-22 10:32 ` Jan Kiszka
2019-02-25 16:03 ` Henning Schild
2018-02-21 15:30 ` [PATCH 0/1] Remove hard-code distro name " Claudius Heine
2018-02-21 15:51 ` Hombourger, Cedric
2018-02-21 16:10 ` Claudius Heine [this message]
2018-03-02 12:34 ` Alexander Smirnov
2018-03-07 11:24 ` Hombourger, Cedric
2018-03-15 13:59 ` Alexander Smirnov
2018-04-04 6:25 ` chombourger
2018-04-04 10:43 ` Jan Kiszka
2018-04-04 10:49 ` Cedric Hombourger
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=d0e7c3c7-3e1e-215d-4d00-c02209ddd103@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=Cedric_Hombourger@mentor.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