public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: Cedric Hombourger <Cedric_Hombourger@mentor.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH 0/1] Remove hard-code distro name in the multistrap template
Date: Wed, 21 Feb 2018 16:30:26 +0100	[thread overview]
Message-ID: <b566b63a-acf9-6c9b-8a55-81fc760103e9@siemens.com> (raw)
In-Reply-To: <20180221131924.4744-1-Cedric_Hombourger@mentor.com>

Hi,

On 02/21/2018 02:19 PM, Cedric Hombourger wrote:
> As users may define their own distro name, the multistrap configuration template
> we provide should not have it hard-coded to "isar" but use whatever DEBDISTRONAME
> setting we receive. Failure to do will result in fetch failures from the isar-apt
> source feed.

Just FYI: this fix is also included in my multistrap removal patchset.

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

  parent reply	other threads:[~2018-02-21 15:30 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 ` Claudius Heine [this message]
2018-02-21 15:51   ` [PATCH 0/1] Remove hard-code distro name " Hombourger, Cedric
2018-02-21 16:10     ` Claudius Heine
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=b566b63a-acf9-6c9b-8a55-81fc760103e9@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