All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christophe Varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Cc: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
Subject: [Notice] multipath-tools changes upstream
Date: Tue, 15 Apr 2008 19:02:08 +0200	[thread overview]
Message-ID: <1208278929.11770.62.camel@plop> (raw)

Hi,

please take notice I updated the upstream git tree for the
multipath-tools project. This tree includes lots of code shuffling :

1) prioritizers as dlopen'ed shared libs (/lib/libmultipath/libprio*.so)
2) checkers as dlopen'ed shared libs (/lib/libmultipath/libcheck*.so)

Consequences :
The multipath tool is about to get shot for good
The klibc build is gone

Please review, and comment.

Regards,
cvaroqui

             reply	other threads:[~2008-04-15 17:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15 17:02 Christophe Varoqui [this message]
2008-04-17 18:25 ` [Notice] multipath-tools changes upstream Benjamin Marzinski
2008-04-17 20:48   ` Mike Anderson
2008-04-18 14:45 ` Hannes Reinecke
2008-05-14 15:21 ` Kiyoshi Ueda
  -- strict thread matches above, loose matches on Subject: below --
2008-05-14 20:21 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=1208278929.11770.62.camel@plop \
    --to=christophe.varoqui@free.fr \
    --cc=dm-devel@redhat.com \
    --cc=k-ueda@ct.jp.nec.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.