From: Mike Anderson <andmike@linux.vnet.ibm.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [Notice] multipath-tools changes upstream
Date: Thu, 17 Apr 2008 13:48:13 -0700 [thread overview]
Message-ID: <20080417204813.GC22737@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080417182526.GH3116@ether.msp.redhat.com>
Benjamin Marzinski <bmarzins@redhat.com> wrote:
> On Tue, Apr 15, 2008 at 07:02:08PM +0200, Christophe Varoqui wrote:
> > 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.
>
> I'm not able to update my copy of the repository, or clone a new one.
> Am I the only one?
>
It is working for me.
I just pulled the other day post the email.
git-head on my tree is currently at:
e22cda64d35235a2b6511cfb589710c3bd3202e0
I just did a git-pull and it indicated that I was up to date.
I am pulling from:
remote.origin.url=git://git.kernel.org/pub/scm/linux/storage/multipath-tools/.git
-andmike
--
Michael Anderson
andmike@linux.vnet.ibm.com
next prev parent reply other threads:[~2008-04-17 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 17:02 [Notice] multipath-tools changes upstream Christophe Varoqui
2008-04-17 18:25 ` Benjamin Marzinski
2008-04-17 20:48 ` Mike Anderson [this message]
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=20080417204813.GC22737@linux.vnet.ibm.com \
--to=andmike@linux.vnet.ibm.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 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.