From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 0/6] pre-processing pipeline and transient package replacement
Date: Thu, 25 Apr 2019 12:06:20 +0200 [thread overview]
Message-ID: <20190425100620.GI21981@yssyq.m.ilbers.de> (raw)
In-Reply-To: <9ef21f4f-fc21-1908-0115-00a8660fd509@siemens.com>
On Wed, Apr 24, 2019 at 04:55:36PM +0200, Claudius Heine wrote:
> Just applying some cleanup and refactoring patches from a series in order,
> without applying the feature (if it contains one) or some other latter
> problematic patches is fine as well IMO.
If you are aware which patches do and which don't cause the problems and would
like to get them applied faster, one option is to resend the partial working
series first and post the rest after sorting out the issues.
With kind regards,
Baurzhan.
prev parent reply other threads:[~2019-04-25 10:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 11:25 claudius.heine.ext
2019-04-18 11:25 ` [PATCH 1/6] split up isar-bootstrap helper and implement pre-process pipeline claudius.heine.ext
2019-04-18 11:25 ` [PATCH 2/6] meta: remove transient package support claudius.heine.ext
2019-04-18 11:25 ` [PATCH 3/6] meta/classes: add image-locales-extension class claudius.heine.ext
2019-04-18 11:25 ` [PATCH 4/6] meta/classes: add image-account-extension class claudius.heine.ext
2019-04-18 11:25 ` [PATCH 5/6] doc: update description of image customization claudius.heine.ext
2019-04-18 11:25 ` [PATCH 6/6] doc: some fixes claudius.heine.ext
2019-04-22 14:09 ` [PATCH 0/6] pre-processing pipeline and transient package replacement Maxim Yu. Osipov
2019-04-24 7:11 ` Claudius Heine
2019-04-24 8:18 ` Maxim Yu. Osipov
2019-04-24 8:38 ` Claudius Heine
2019-04-24 14:38 ` Baurzhan Ismagulov
2019-04-24 14:55 ` Claudius Heine
2019-04-25 10:06 ` Baurzhan Ismagulov [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=20190425100620.GI21981@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