From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Benjamin Marzinski <bmarzins@redhat.com>,
Hannes Reinecke <hare@suse.de>, Martin Wilck <mwilck@suse.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] multipath-tools: replace multipath configuration output
Date: Wed, 7 Dec 2016 23:48:33 +0100 [thread overview]
Message-ID: <7340eba3-ae61-9933-597e-56c176d22bef@gmail.com> (raw)
In-Reply-To: <20161202035207.GG3099@octiron.msp.redhat.com>
On 12/02/2016 04:52 AM, Benjamin Marzinski wrote:
> I don't really see the need for this change. But we wouldn't be pulling
> it in until the next major RHEL release [...]
BTW, do you(SUSE/RH) have any distro fixes/features pending for upstream?
next prev parent reply other threads:[~2016-12-07 22:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 22:44 [PATCH] multipath-tools: replace multipath configuration output Xose Vazquez Perez
2016-11-25 9:00 ` Martin Wilck
2016-11-26 9:21 ` Christophe Varoqui
2016-12-02 3:52 ` Benjamin Marzinski
2016-12-07 22:48 ` Xose Vazquez Perez [this message]
2016-12-14 18:29 ` Christophe Varoqui
2017-02-22 16:20 ` multipath-tools: Fixes/features for upstream Xose Vazquez Perez
2017-02-23 6:56 ` Hannes Reinecke
2016-12-07 15:44 ` [PATCH] multipath-tools: replace multipath configuration output Xose Vazquez Perez
2016-12-07 16:17 ` Martin Wilck
[not found] ` <c78854cd-f7f2-77ef-2d19-a5ff236e9a37@gmail.com>
2017-08-20 0:47 ` Xose Vazquez Perez
-- strict thread matches above, loose matches on Subject: below --
2017-04-08 13:30 Xose Vazquez Perez
2017-04-12 7:35 ` Christophe Varoqui
2017-04-13 23:56 ` Xose Vazquez Perez
2017-04-14 8:29 ` Christophe Varoqui
2017-04-18 0:07 [PATCH] multipath-tools: Replace " Xose Vazquez Perez
2017-05-18 0:06 ` Xose Vazquez Perez
2017-06-21 10:33 ` Christophe Varoqui
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=7340eba3-ae61-9933-597e-56c176d22bef@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=mwilck@suse.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