public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] doc/user_manual: Update after images per machine separation
Date: Thu, 14 Mar 2019 12:31:21 +0100	[thread overview]
Message-ID: <20190314113121.GD16465@yssyq.m.ilbers.de> (raw)
In-Reply-To: <9d284bca-29a0-92d6-5711-0ee1689e0a3c@siemens.com>

On Thu, Mar 14, 2019 at 08:14:34AM +0100, Jan Kiszka wrote:
> > diff --git a/RECIPE-API-CHANGELOG.md b/RECIPE-API-CHANGELOG.md
...
> > -`IMAGE-DISTRO-MACHINE.TYPE`. This scheme was already used for ext4/wic images
> > +`IMAGE-MACHINE-DISTRO-MACHINE.TYPE`. This scheme was already used for ext4/wic images
> 
> Reading this again: Where does the first MACHINE in this file name come
> from? Maybe it can be avoided, now that we officially name image recipes
> after the machine.

I also don't like changing the UX in this version of the patch. Since we are
going to update tmp/work w.r.t. ${MACHINE} anyway, I suggest that we merge and
document the original workaround [1] that unbreaks the stuff and quickly move
forward with the critical patches and the right fix.

1. https://groups.google.com/d/msg/isar-users/9CJ1QmMbKYU/Sy8A6q6FBgAJ

With kind regards,
Baurzhan.

  reply	other threads:[~2019-03-14 11:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 20:27 [PATCH 1/2] meta-isar: Separate images per MACHINE Maxim Yu. Osipov
2019-03-12 20:27 ` [PATCH 2/2] doc/user_manual: Update after images per machine separation Maxim Yu. Osipov
2019-03-14  7:14   ` Jan Kiszka
2019-03-14 11:31     ` Baurzhan Ismagulov [this message]
2019-03-14 12:08       ` Jan Kiszka
2019-03-13 16:42 ` [PATCH 1/2] meta-isar: Separate images per MACHINE Maxim Yu. Osipov
2019-03-14  7:15   ` Jan Kiszka
2019-03-14  7:21   ` Claudius Heine
2019-03-14  7:28     ` Jan Kiszka
2019-03-14  8:07       ` Claudius Heine
2019-03-14  8:20         ` Claudius Heine
2019-03-14 12:22           ` Claudius Heine
2019-03-15  9:02     ` Maxim Yu. Osipov
2019-03-15 10:25       ` Claudius Heine
2019-03-15 11:22         ` Maxim Yu. Osipov
2019-03-15 14:28         ` Baurzhan Ismagulov

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=20190314113121.GD16465@yssyq.m.ilbers.de \
    --to=ibr@radix50.net \
    --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