From: Benjamin Marzinski <bmarzins@redhat.com>
To: christophe.varoqui@opensvc.com,
device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH] [PATCH] option to multipath to not modify the bindinfs file
Date: Thu, 2 Sep 2010 12:06:32 -0500 [thread overview]
Message-ID: <20100902170632.GA7185@ether.msp.redhat.com> (raw)
In-Reply-To: <1282900690.8426.6.camel@localhost>
On Fri, Aug 27, 2010 at 11:18:10AM +0200, Christophe Varoqui wrote:
>
> On jeu., 2010-08-26 at 22:39 -0700, Malahal Naineni wrote:
> > Christophe, Hannes: any comments on this approach to fix the uuid issue
> > reported earlier here
> > http://permalink.gmane.org/gmane.linux.kernel.device-mapper.devel/12027
> >
> The approach seems fine to me.
> Hannes, Ben, would suse and redhat use this in their early userspace ?
Sure.
-Ben
>
> Cheers,
> cvaroqui
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2010-09-02 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 22:57 [PATCH] [PATCH] option to multipath to not modify the bindinfs file Malahal Naineni
2010-08-27 5:39 ` Malahal Naineni
2010-08-27 9:18 ` Christophe Varoqui
2010-08-30 15:07 ` Hannes Reinecke
2010-09-02 17:06 ` Benjamin Marzinski [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=20100902170632.GA7185@ether.msp.redhat.com \
--to=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.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;
as well as URLs for NNTP newsgroup(s).