From: Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>
To: Hal Rosenstock <hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org"
<ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>
Subject: Re: RFC: Splitting of the management git tree in Open Fabrics
Date: Thu, 2 Sep 2010 14:05:39 -0700 [thread overview]
Message-ID: <20100902140539.edebfccb.weiny2@llnl.gov> (raw)
In-Reply-To: <AANLkTimyyKEnFe3yuRBPzMp5Vx21PMyq=yJQMWyph3cu-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Thu, 2 Sep 2010 13:36:34 -0700
Hal Rosenstock <hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Ira,
>
> On Tue, Aug 31, 2010 at 3:51 PM, Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org> wrote:
> > As I briefly mentioned in an email to Yevgeny regarding libibumad ABI's; I
> > believe it is time to break up the management git tree.
>
> I think these are separate issues. What are you trying to achieve by
> doing this ?
Yes they are separate issues. That is why I started this thread.
When I said "I think it is time to break up the management git tree" I was
thinking along the lines that umad and mad are libraries used by tools outside
of OpenSM and infiniband-diags. As such I think it would be easier to
maintain them as separate trees. This includes maintaining branches and
versions with consistent ABI's.
Ira
>
> -- Hal
>
> > With GA of OFED 1.5.2 scheduled for Sept 13, I would like to request comments
> > from the community about the following split after that GA.
> >
> > On openfabrics.org/git split management.git into the following trees.
> >
> > openfabrics.org/git/infiniband-diags.git
> > openfabrics.org/git/libibumad.git
> > openfabrics.org/git/libibmad.git
> > openfabrics.org/git/opensm.git
> >
> > Sasha can populate those from the current management tree. We believe there
> > are git commands which will do this without losing any history from the git
> > trees.
> >
> > Vlad, what changes would you have to make in the OFED build to accommodate
> > these packages being in separate git trees?
> >
> > Any other concerns or comments?
> >
> > Thanks,
> > Ira
> >
> > --
> > Ira Weiny
> > Math Programmer/Computer Scientist
> > Lawrence Livermore National Lab
> > 925-423-8008
> > weiny2-i2BcT+NCU+M@public.gmane.org
> > --
> > 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
> >
>
--
Ira Weiny
Math Programmer/Computer Scientist
Lawrence Livermore National Lab
925-423-8008
weiny2-i2BcT+NCU+M@public.gmane.org
next prev parent reply other threads:[~2010-09-02 21:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 19:51 RFC: Splitting of the management git tree in Open Fabrics Ira Weiny
[not found] ` <20100831125159.98e6d201.weiny2-i2BcT+NCU+M@public.gmane.org>
2010-09-01 6:15 ` Vladimir Sokolovsky
2010-09-01 7:21 ` Hefty, Sean
2010-09-02 20:36 ` RFC: " Hal Rosenstock
[not found] ` <AANLkTimyyKEnFe3yuRBPzMp5Vx21PMyq=yJQMWyph3cu-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-02 21:05 ` Ira Weiny [this message]
2011-01-30 17:41 ` Sasha Khapyorsky
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=20100902140539.edebfccb.weiny2@llnl.gov \
--to=weiny2-i2bct+ncu+m@public.gmane.org \
--cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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