From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: proper wic integration
Date: Tue, 23 Jan 2018 13:46:25 +0100 [thread overview]
Message-ID: <1258d45d-e88b-974f-dc20-dccacbfa6fc3@siemens.com> (raw)
In-Reply-To: <20180123115459.GB4542@yssyq.radix50.net>
On 2018-01-23 12:54, Baurzhan Ismagulov wrote:
> On Fri, Jan 19, 2018 at 01:18:51PM +0100, Henning Schild wrote:
>> To get that merged i will first move to an untouched version of wic and
>> rebase it on top of that.
>
> I'd strongly suggest that you clean up this version so that it is merged and
> Christian can use it, and refactor wic in a separate series.
Patches are there, they surely need some cleanups, but I don't see your
point in reordering.
In the end, the effort to remove the upstream wic modification wasn't
that excessive as we feared. In fact, it would have been probably
simpler to go that way in the beginning.
But Henning is on vacation this week, so don't expect an update before
mid of next week.
Jan
next prev parent reply other threads:[~2018-01-23 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 12:18 Henning Schild
2018-01-19 14:02 ` Baurzhan Ismagulov
2018-01-19 14:15 ` Henning Schild
2018-01-23 11:54 ` Baurzhan Ismagulov
2018-01-23 12:46 ` Jan Kiszka [this message]
2018-01-24 14:19 ` 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=1258d45d-e88b-974f-dc20-dccacbfa6fc3@siemens.com \
--to=jan.kiszka@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