From: Jeff Becker <Jeffrey.C.Becker-NSQ8wuThN14@public.gmane.org>
To: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Cc: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>,
Linux RDMA list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org"
<ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org>,
Vladimir Sokolovsky
<vlad-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
Subject: Re: Where is the latest GIT for opensm?
Date: Thu, 7 Oct 2010 08:47:18 -0700 [thread overview]
Message-ID: <4CADEB86.10408@nasa.gov> (raw)
In-Reply-To: <20101007023314.GA21206-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
Hi Jason.
On 10/06/10 19:33, Jason Gunthorpe wrote:
> Hey Sasha,
>
> Can you tell me where the latest git repository for OpenSM is these
> days? There doesn't seem to be anything recent on the OFA server,
> ie
>
> git://git.openfabrics.org/~sashak/management.git
>
> Is quite old.
Yes. The problem is that most of the developers have not yet moved to
the new server. For your example, I had to do:
git clone git://69.55.239.13/~sashak/management.git
to get the up to date repo. on the old server.
It would be great if developers could move their git repo's to the new
server so OFA can stop using (and paying) for the old server. Vlad sent
out a note about this earlier.
Thanks.
-jeff
> Thanks,
> Jason
--
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:[~2010-10-07 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 2:33 Where is the latest GIT for opensm? Jason Gunthorpe
[not found] ` <20101007023314.GA21206-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-10-07 15:47 ` Jeff Becker [this message]
[not found] ` <4CADEB86.10408-NSQ8wuThN14@public.gmane.org>
2010-10-07 16:50 ` Jason Gunthorpe
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=4CADEB86.10408@nasa.gov \
--to=jeffrey.c.becker-nsq8wuthn14@public.gmane.org \
--cc=ewg-ZwoEplunGu1OwGhvXhtEPSCwEArCW2h5@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org \
--cc=vlad-VPRAkNaXOzVS1MOuV/RT9w@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