From: "Frank Ch. Eigler" <fche@redhat.com>
To: Matt Schulte <schultetwin1@gmail.com>
Cc: T R <trebele@outlook.com>,
"elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: Inquiry about Development Features and Integration of Source Code Version Control Systems
Date: Wed, 10 Apr 2024 12:07:15 -0400 [thread overview]
Message-ID: <20240410160715.GC30102@redhat.com> (raw)
In-Reply-To: <CAJqzY_5orQtsj=EKyS+fkDr=7UXbp8HRP3sS5_J60ZZ-TGZsKQ@mail.gmail.com>
Hi -
> Support for reading source code directly from a code hosting service
> (such as GitHub) has been supported for years by Microsoft via
> SourceLink[1]. [...]
Thanks for that reminder. Yeah, eventually that could be an alternate
way.
> [...]
> > Can you explain under what situations you think this would be helpful?
>
> I can only think about situations that involve closed source software.
> In my experience, companies shipping closed source software have
> restrictions about where source code can be placed.
i.e., a situation where even an internal debuginfod instance cannot be
trusted with the source code, but some version control system can be?
- FChE
next prev parent reply other threads:[~2024-04-10 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 5:57 T R
2024-04-10 14:26 ` Frank Ch. Eigler
2024-04-10 16:01 ` Matt Schulte
2024-04-10 16:07 ` Frank Ch. Eigler [this message]
2024-04-11 4:55 ` Matt Schulte
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=20240410160715.GC30102@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=schultetwin1@gmail.com \
--cc=trebele@outlook.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 read-only IMAP folder(s) and NNTP newsgroup(s).