Linux Device Mapper development
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Changwei Ge <ge.changwei@h3c.com>,
	"dm-devel@redhat.com" <dm-devel@redhat.com>,
	Christophe Varoqui <christophe.varoqui@opensvc.com>
Subject: Re: [RFC] where is upstream multipath-tool git repo
Date: Fri, 27 Oct 2017 18:13:36 +0200	[thread overview]
Message-ID: <6229cb6f-7e16-eae3-d8ee-031197de6128@gmail.com> (raw)
In-Reply-To: <63ADC13FD55D6546B7DECE290D39E373CED71927@H3CMLB14-EX.srv.huawei-3com.com>

On 10/27/2017 04:31 AM, Changwei Ge wrote:

> Does anyone have any idea where I can find the upstream multipath-tool 
> git repository including the lately fixed issues?

Full project info at: http://christophe.varoqui.free.fr/

There are still pending patches: https://marc.info/?l=dm-devel&m=150634203214761

      reply	other threads:[~2017-10-27 16:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27  2:31 [RFC] where is upstream multipath-tool git repo Changwei Ge
2017-10-27 16:13 ` Xose Vazquez Perez [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=6229cb6f-7e16-eae3-d8ee-031197de6128@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@redhat.com \
    --cc=ge.changwei@h3c.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