From: Leon Romanovsky <leon-2ukJVAZIZ/Y@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma
(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Hal Rosenstock
(hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org)"
<hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>,
"Wan, Kaike" <kaike.wan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Weiny, Ira" <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: Move of upstream librdmacm and ibacm git trees
Date: Sun, 6 Mar 2016 16:38:32 +0200 [thread overview]
Message-ID: <20160306143832.GG13396@leon.nu> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A82373AB010AC9-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Thu, Feb 18, 2016 at 07:30:41PM +0000, Hefty, Sean wrote:
> I have moved the upstream git trees for the librdmacm and ibacm from
>
> git.openfabrics.org --> github.com
>
> The new trees were added to the ofiwg project:
>
> https://github.com/ofiwg/librdmacm.git
> https://github.com/ofiwg/ibacm.git
>
> This will allow developers to take advantage of github features -- discussion tracking, coverity code analysis, continuous integration build testing, multiple maintainers, etc.
Do you plan to copy github pull requests on this mailing list too? So
all developers will be able to follow the development and not the github
users only.
>
> - Sean
> --
> 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
--
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
next prev parent reply other threads:[~2016-03-06 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 19:30 Move of upstream librdmacm and ibacm git trees Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373AB010AC9-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-02-19 6:49 ` Vasiliy Tolstov
[not found] ` <CACaajQsQm49Birn-WjiRPr71Xj6zBYVqDJzVMpNzVDoHUBU0hg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-19 17:31 ` Hefty, Sean
2016-03-06 14:38 ` Leon Romanovsky [this message]
[not found] ` <20160306143832.GG13396-2ukJVAZIZ/Y@public.gmane.org>
2016-03-07 17:06 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373AB01FFCC-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-03-07 18:03 ` Or Gerlitz
[not found] ` <CAJ3xEMgr2jMkKDVSHt1GM0O0E-MgWXANTuMQ3NgZOdBEZtMYsA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-07 18:10 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373AB0200F1-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2016-03-07 20:35 ` leon-2ukJVAZIZ/Y
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=20160306143832.GG13396@leon.nu \
--to=leon-2ukjvaziz/y@public.gmane.org \
--cc=hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org \
--cc=ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kaike.wan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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