From: Alex Netes <alexne-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
EWG <ewg-G2znmakfqn7U1rindQTSdQ@public.gmane.org>
Subject: Re: OFA management tree seperation
Date: Wed, 23 Feb 2011 12:12:40 +0200 [thread overview]
Message-ID: <20110223101240.GA9811@calypso.voltaire.com> (raw)
In-Reply-To: <20110213225909.GA4506-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
On 15:59 Sun 13 Feb , Jason Gunthorpe wrote:
> On Sun, Feb 13, 2011 at 09:55:50AM +0200, Alex Netes wrote:
> >
> > We finished the management tree seperation.
> > From now on, Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org> takes the responsibility for maitaining libibmad and
> > infiniband-diags. His trees are:
> >
> > git://git.openfabrics.org/~iraweiny/libibmad
> > git://git.openfabrics.org/~iraweiny/infiniband-diags
> >
> > libibumad, opensm and ibsim trees stays under my responsibility:
> >
> > git://git.openfabrics.org/~alexnetes/libibumad
> > git://git.openfabrics.org/~alexnetes/opensm
> > git://git.openfabrics.org/~alexnetes/ibsim
>
> Can you please include the OpenSm 3.2.6 and related branch and tags in
> your repository?
>
Done. OpenSM 3.2.6 resides on opensm-3.2 branch as before.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-02-23 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 7:55 OFA management tree seperation Alex Netes
[not found] ` <20110213075550.GB5697-iQai9MGU/dyyaiaB+Ve85laTQe2KTcn/@public.gmane.org>
2011-02-13 22:59 ` Jason Gunthorpe
[not found] ` <20110213225909.GA4506-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2011-02-23 10:12 ` Alex Netes [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=20110223101240.GA9811@calypso.voltaire.com \
--to=alexne-smomgflxvozwk0htik3j/w@public.gmane.org \
--cc=ewg-G2znmakfqn7U1rindQTSdQ@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=weiny2-i2BcT+NCU+M@public.gmane.org \
/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