From: "Jason Pyeron" <jpyeron@pdinc.us>
To: "'Jesse Earles'" <jesse.earles@aero.org>
Cc: <git@vger.kernel.org>
Subject: RE: Are there MPU/SKU's for these products?
Date: Wed, 24 Jun 2020 12:07:53 -0400 [thread overview]
Message-ID: <262201d64a41$9e1cb720$da562560$@pdinc.us> (raw)
In-Reply-To: <BY5PR09MB4504AD01DDA757120DCC79ABFF950@BY5PR09MB4504.namprd09.prod.outlook.com>
That is our source code stock tag.
> -----Original Message-----
> From: Jesse Earles <jesse.earles@aero.org>
> Sent: Wednesday, June 24, 2020 12:06 PM
> To: Jason Pyeron <jpyeron@pdinc.us>
> Cc: git@vger.kernel.org
> Subject: RE: Are there MPU/SKU's for these products?
>
> Thanks, but I was referring to if there was a Manufacturing Part Number or a Stock Keeping Unit number
> for this product. I believe we already have the unique ID entered in another field, so that part
> should be good.
>
>
>
>
> Jesse Earles
> Desktop Support Specialist
> EIS/IT Operations
> Digital Intelligence Systems, LLC (DISYS)
> The Aerospace Corporation
> 14745 Lee Rd. Chantilly, VA 20151
>
>
>
> -----Original Message-----
> From: Jason Pyeron <jpyeron@pdinc.us>
> Sent: Wednesday, June 24, 2020 11:59 AM
> To: Jesse Earles <jesse.earles@aero.org>
> Cc: git@vger.kernel.org
> Subject: RE: Are there MPU/SKU's for these products?
>
> The unique identifier for that version is: e7e07d5a4fcc2a203d9873968ad3e6bd4d7419d7
>
> commit e7e07d5a4fcc2a203d9873968ad3e6bd4d7419d7 (tag: v2.12.0)
> Author: Junio C Hamano <gitster@pobox.com>
> Date: Fri Feb 24 10:49:58 2017 -0800
>
> Git 2.12
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
>
>
> > -----Original Message-----
> > From: git-owner@vger.kernel.org <git-owner@vger.kernel.org> On Behalf
> > Of Jesse Earles
> > Sent: Wednesday, June 24, 2020 11:43 AM
> > To: git@vger.kernel.org
> > Subject: Are there MPU/SKU's for these products?
> >
> > Hello,
> >
> > I am working with my software team on updating their internal catalog
> > with current and accurate info and am needing to find the MPN/SKU for
> > "Software Freedom Conservancy | Git | v2.12.0". I'm not certain if
> > there even is one as I assume this is open-sourced, but I figured I'd reach out to get confirmation
> before I make an internal SKU for our records. Thanks.
> >
> >
> > Jesse Earles
> > Desktop Support Specialist
> > EIS/IT Operations
> > Digital Intelligence Systems, LLC (DISYS) The Aerospace Corporation
> > 14745 Lee Rd. Chantilly, VA 20151
> >
> >
> >
>
>
next prev parent reply other threads:[~2020-06-24 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 15:42 Are there MPU/SKU's for these products? Jesse Earles
2020-06-24 15:59 ` Jason Pyeron
2020-06-24 16:05 ` Jesse Earles
2020-06-24 16:07 ` Jason Pyeron [this message]
2020-06-24 16:13 ` Jesse Earles
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='262201d64a41$9e1cb720$da562560$@pdinc.us' \
--to=jpyeron@pdinc.us \
--cc=git@vger.kernel.org \
--cc=jesse.earles@aero.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;
as well as URLs for NNTP newsgroup(s).