From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: "Andreas J. Reichel" <andreas.reichel.ext@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Rebase your patchset to 'next'
Date: Wed, 27 Mar 2019 16:34:34 +0100 [thread overview]
Message-ID: <4486523e-8770-9c3b-4565-5e07942076dc@ilbers.de> (raw)
Hi Andreas,
The reason of the latest CI failures on isar-build.org is that you have
to rebase against the latest next (the problem is fixed in 9cbcdd69).
Just my couple of roubles,
Maxim.
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
reply other threads:[~2019-03-27 15:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4486523e-8770-9c3b-4565-5e07942076dc@ilbers.de \
--to=mosipov@ilbers.de \
--cc=andreas.reichel.ext@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