From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'COLLINS,
ROGER W GG-12 USAF NASIC/SCPW'" <roger.collins@us.af.mil>,
"'Stefan Beller'" <sbeller@google.com>
Cc: <git@vger.kernel.org>
Subject: RE: Git Vendor Support
Date: Mon, 13 Mar 2017 11:34:44 -0400 [thread overview]
Message-ID: <000f01d29c0f$5ac81430$10583c90$@nexbridge.com> (raw)
In-Reply-To: <C81F618483B6A04381181BA5435FB9706CFF7611@52ZHTX-D03-05E.area52.afnoapps.usaf.mil>
On March 13, 2017 10:34 AM, COLLINS, ROGER W GG-12 USAF NASIC/SCPW wrote:
>Thanks for the reply!
>>On March 10, 2017 11:48 AM, Stefan Beller wrote
>>On Fri, Mar 10, 2017 at 8:13 AM, COLLINS, ROGER W GG-12 USAF NASIC/SCPW <roger.collins@us.af.mil> wrote:
>>> ALCON,
>>>
>>> Is there is a specific group or vendor backing Git?
>>https://sfconservancy.org/ takes care of the financial needs of the community.
>>> active support
>>I guess companies that make money primarily via Git hosting (e.g. one of Github, GitLab, Atlassian, Bitbucket) *may* be interested in active support.
I have heard there are companies who provide porting, technical and user support for git on some platforms and in some environments. It might be worth checking in the platform communities specifically for companies that are servicing the platforms. I am well connected in the HPE NonStop community if that's a help.
Cheers,
Randall
next prev parent reply other threads:[~2017-03-13 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 16:13 Git Vendor Support COLLINS, ROGER W GG-12 USAF NASIC/SCPW
2017-03-10 16:48 ` Stefan Beller
2017-03-13 14:34 ` COLLINS, ROGER W GG-12 USAF NASIC/SCPW
2017-03-13 15:34 ` Randall S. Becker [this message]
2017-03-10 16:57 ` Konstantin Khomoutov
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='000f01d29c0f$5ac81430$10583c90$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=roger.collins@us.af.mil \
--cc=sbeller@google.com \
/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;
as well as URLs for NNTP newsgroup(s).