From: Stefan Beller <sbeller@google.com>
To: "Robertson, Todd" <Todd.Robertson@alere.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Questions about validation/verification done for Git Software
Date: Mon, 8 May 2017 10:21:05 -0700 [thread overview]
Message-ID: <CAGZ79kaLMHWth_t7LBpvtAKJQvseS34+RCKoedeqFosUxOiaPg@mail.gmail.com> (raw)
In-Reply-To: <504208edac024b2dba0c1743dc86683e@AMUSATLWP20005.alereinc.com>
On Mon, May 8, 2017 at 10:14 AM, Robertson, Todd
<Todd.Robertson@alere.com> wrote:
> Hello,
>
> I'm a Sr. Software Quality Assurance Engineer at Epocal Inc. in Ottawa, Ontario,
> Canada. We are a medical device manufacturer that is required to comply with
> the Food & Drug Administration's (FDA) regulations.
> I'm in charge of what is known as Non-Product Software, essentially any piece of
> SW that is used in the day-to-day work of creating our products.
> Part of complying with the FDA regulations is to ensure that all Non-Product Software
> has been validated.
>
> Some of our engineers are planning on using your software "Git" for their software
> development processes (latest version) to replace our current software "SVN" and I was
> hoping you could answer some questions for me?
How is svn validated for you?
> Are you able to provide me with a copy of your Test Plans and/or Test Cases for the "Git" product?
Tests are found inside the t/ directory in your copy of Git[1].
[1] obtained e.g. via "git clone https://github.com/git/git"
Note that these are just tests; nothing formal attached.
> Is the software FDA certified?
I am not aware of that.
Checkout https://git-scm.com/ and for legal questions contact
https://sfconservancy.org/ (via https://git-scm.com/sfc)
next prev parent reply other threads:[~2017-05-08 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 17:14 Questions about validation/verification done for Git Software Robertson, Todd
2017-05-08 17:21 ` Stefan Beller [this message]
2017-05-09 1:51 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGZ79kaLMHWth_t7LBpvtAKJQvseS34+RCKoedeqFosUxOiaPg@mail.gmail.com \
--to=sbeller@google.com \
--cc=Todd.Robertson@alere.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).