From: Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>
To: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org
Subject: RFC: Splitting of the management git tree in Open Fabrics
Date: Tue, 31 Aug 2010 12:51:59 -0700 [thread overview]
Message-ID: <20100831125159.98e6d201.weiny2@llnl.gov> (raw)
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.
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
next reply other threads:[~2010-08-31 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-31 19:51 Ira Weiny [this message]
[not found] ` <20100831125159.98e6d201.weiny2-i2BcT+NCU+M@public.gmane.org>
2010-09-01 6:15 ` RFC: Splitting of the management git tree in Open Fabrics 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
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=20100831125159.98e6d201.weiny2@llnl.gov \
--to=weiny2-i2bct+ncu+m@public.gmane.org \
--cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@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