From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'ankostis'" <ankostis@gmail.com>
Cc: "'Git Mailing List'" <git@vger.kernel.org>,
"'Jason Cooper'" <git@lakedaemon.net>
Subject: RE: Unconventional roles of git
Date: Tue, 28 Feb 2017 10:27:11 -0500 [thread overview]
Message-ID: <006d01d291d7$25bd8820$71389860$@nexbridge.com> (raw)
In-Reply-To: <CA+dhYEXtkrZk4g7KHUK_JPWCE=o4cCC9hU8inp1GJuk-V9gtew@mail.gmail.com>
>From: ankostis [mailto:ankostis@gmail.com]
>Sent: February 28, 2017 8:01 AM
>To: Randall S. Becker <rsbecker@nexbridge.com>
>Cc: Git Mailing List <git@vger.kernel.org>; Jason Cooper <git@lakedaemon.net>
>Subject: Re: Unconventional roles of git
>On 27 February 2017 at 20:16, Randall S. Becker <mailto:rsbecker@nexbridge.com> wrote:
>> On February 26, 2017 6:52 AM, Kostis Anagnostopoulos <mailto:ankostis@gmail.com> worte:
>>> On 26 February 2017 at 02:13, Jason Cooper <mailto:git@lakedaemon.net> wrote:
>>> > As someone looking to deploy (and having previously deployed) git in
>>> > unconventional roles, I'd like to add ...
>>>
>>> We are developing a distributed storage for type approval files regarding all
>>> vehicles registered in Europe.[1] To ensure integrity even after 10 or 30
>>> years, the hash of a commit of these files (as contained in a tag) are to be
>>> printed on the the paper certificates.
>>>
>>> - Can you provide some hints for other similar unconventional roles of git?
>>> - Any other comment on the above usage of git are welcomed.
>>
>> I am involved in managing manufacturing designs and parts configurations and approvals with git being intimately involved in the process of developing and deploying tested designs to >computerized manufacturing environments. It's pretty cool actually to see things become real.
>Thanks for the tip.
>Can you provide some links or the legislation involved?
I have not done much in the way of write-ups other than PowerPoint-based training material for the companies involved. So far, this does not seem to be subject to regulatory or legislation - but that depends on what is being manufactured. In the current situation, I'm helping organize cabinet parts, components, GCode, optimizations, and other arcane artifacts in the woodworking community for CNC and related process support. It is an evolving domain. I do wish that Cloud providers like Atlassian would provide more comprehensive integrated code reviews (a.k.a. Gerrit) for some of this work. Surprisingly that's a harder sell to dedicate a server internally.
Cheers,
Randall
prev parent reply other threads:[~2017-02-28 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 11:51 Unconventional roles of git ankostis
2017-02-27 19:16 ` Randall S. Becker
[not found] ` <CA+dhYEXtkrZk4g7KHUK_JPWCE=o4cCC9hU8inp1GJuk-V9gtew@mail.gmail.com>
2017-02-28 15:27 ` Randall S. Becker [this message]
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='006d01d291d7$25bd8820$71389860$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=ankostis@gmail.com \
--cc=git@lakedaemon.net \
--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).