Linux Device Mapper development
 help / color / mirror / Atom feed
From: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: brian@purestorage.com
Subject: Re: Question about multipath device compiled defaults
Date: Wed, 20 Jan 2016 15:47:57 -0200	[thread overview]
Message-ID: <569FC84D.4070301@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAHZQxyLc3Sn5ycm3YCyVQEA10+rqer1_bmcRrODLrxTh+R1GwQ@mail.gmail.com>

Hi Brian,

On 01/20/2016 02:15 PM, Brian Bunker wrote:
> Any ideas how long it typically takes the distros like RHEL, etc. to
> pull these changes down, or do they need to be pinged explicitly that
> there are changes available that we want them to consider?

It's a good idea to let them know (e.g., bug/feature report).
I've worked a bit w/ Ubuntu, RHEL, and SLES.

Even though the changes might eventually make downstream, some distros
won't pull everything (reasonably), but only the pieces they find/know
to be required or desired by users/customers -- specially on released/
stable distro versions.

So, letting them know / ask for consideration usually helps.

-- 
Mauricio Faria de Oliveira
IBM Linux Technology Center

      reply	other threads:[~2016-01-20 17:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05  6:59 Question about multipath device compiled defaults Doron Tal1
2016-01-19 16:35 ` Mauricio Faria de Oliveira
2016-01-19 16:48   ` Christophe Varoqui
2016-01-19 22:17     ` Brian Bunker
2016-01-20  6:58       ` Christophe Varoqui
2016-01-20 16:15         ` Brian Bunker
2016-01-20 17:47           ` Mauricio Faria de Oliveira [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=569FC84D.4070301@linux.vnet.ibm.com \
    --to=mauricfo@linux.vnet.ibm.com \
    --cc=brian@purestorage.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