Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Battig, Caleb" <Caleb.Battig@netapp.com>
To: Simon Marchi <simark@simark.ca>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "Lovett, Stuart" <Stuart.Lovett@netapp.com>,
	"Peikes, Wendy" <Wendy.Peikes@netapp.com>
Subject: Re: [PING][PING] Added x86_64 stub for debugging embedded systems running on Intel x86_64 processor architecture.
Date: Wed, 11 Nov 2020 16:39:02 +0000	[thread overview]
Message-ID: <BL0PR06MB4418942D9E738B52B8D843F9E1E80@BL0PR06MB4418.namprd06.prod.outlook.com> (raw)
In-Reply-To: <BL0PR06MB4418724F3D8E23AF98820279E1170@BL0PR06MB4418.namprd06.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 3174 bytes --]

Hi Simon,

I filled out the form you referenced and sent it to assign@gnu.org. I haven't heard anything back from them though, even after I have repeatedly sent reminder emails. I really don't care who has the rights to this software; I just want it to be available for developers to use. Can we move forward with my submission now please?

Thanks,


Caleb Battig

Platform Software Engineer



NetApp

724.741.5226 Direct Phone

Caleb.Battig@netapp.com<mailto:Eugene.Novak@netapp.com>

netapp.com<http://www.netapp.com/us/>


[cid:adb216e4-51dd-49aa-bd63-8bc0c1346ad9]

________________________________
From: Battig, Caleb <Caleb.Battig@netapp.com>
Sent: Wednesday, October 28, 2020 6:11 PM
To: Simon Marchi <simark@simark.ca>; gdb-patches@sourceware.org <gdb-patches@sourceware.org>
Cc: Lovett, Stuart <Stuart.Lovett@netapp.com>; Peikes, Wendy <Wendy.Peikes@netapp.com>
Subject: Re: [PING][PING] Added x86_64 stub for debugging embedded systems running on Intel x86_64 processor architecture.

Simon,

Thanks for sending along that info. I have filled out the form you referenced and sent it to assign@gnu.org. Let me know if you need anything else from me to process my submission.

Thanks,


Caleb Battig

Platform Software Engineer



NetApp

724.741.5226 Direct Phone

Caleb.Battig@netapp.com<mailto:Eugene.Novak@netapp.com>

netapp.com<http://www.netapp.com/us/>


[cid:8bab0f0b-976f-4405-aeeb-cc41947f2d51]

________________________________
From: Simon Marchi <simark@simark.ca>
Sent: Thursday, October 22, 2020 6:47 PM
To: Battig, Caleb <Caleb.Battig@netapp.com>; gdb-patches@sourceware.org <gdb-patches@sourceware.org>
Cc: Lovett, Stuart <Stuart.Lovett@netapp.com>; Peikes, Wendy <Wendy.Peikes@netapp.com>
Subject: Re: [PING][PING] Added x86_64 stub for debugging embedded systems running on Intel x86_64 processor architecture.

NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe.




On 2020-10-22 12:34 p.m., Battig, Caleb wrote:
> Simon,
>
> Any updates on finding reviewers for this? I am going to be out of office all of next week and thus unable to answer further questions.
>
> Thanks,

The problem isn't really reviewers (although I'd appreciate if anybody
who knows the low-level x86-64 bits could take a second look).

I sent an inquiriy to the FSF regarding the licensing, I got a response
that they'll take a look soon.  I'll let you know when I have an answer.
These stubs are licensed "public domain", with no copyright claim, so it
is a bit out of the ordinary for us.  I prefer asking to make sure we do
the right thing.

In any case, you will likely have to file a copyright assignment with
the FSF, where you accept to transfer the copyright on the contributed
code to the FSF.  It would be a good idea to get that started right now,
since it can take a bit of time for them to process it.  This is the
form you need to complete and send them:

    https://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future

Simon

Simon

[-- Attachment #2: Outlook-3slnml45.png --]
[-- Type: image/png, Size: 56478 bytes --]

[-- Attachment #3: Outlook-olzbenrk.png --]
[-- Type: image/png, Size: 56478 bytes --]

  reply	other threads:[~2020-11-11 16:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BL0PR06MB4418CCCF8597C622AC200C61E1300@BL0PR06MB4418.namprd06.prod.outlook.com>
2020-10-12 17:51 ` [PING] " Battig, Caleb
2020-10-19 14:18   ` [PING][PING] " Battig, Caleb
2020-10-19 14:29     ` Simon Marchi
2020-10-19 14:38       ` Battig, Caleb
2020-10-19 14:43         ` Battig, Caleb
2020-10-19 15:45           ` Simon Marchi
2020-10-19 22:23             ` Battig, Caleb
2020-10-20 13:09               ` Simon Marchi
2020-10-20 16:34                 ` Battig, Caleb
2020-10-22 16:34                   ` Battig, Caleb
2020-10-23  0:47                     ` Simon Marchi
2020-10-28 22:11                       ` Battig, Caleb
2020-11-11 16:39                         ` Battig, Caleb [this message]
2020-11-11 20:54                           ` Simon Marchi
2020-11-11 21:58                             ` Battig, Caleb
2020-12-14 15:10                               ` Simon Marchi

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=BL0PR06MB4418942D9E738B52B8D843F9E1E80@BL0PR06MB4418.namprd06.prod.outlook.com \
    --to=caleb.battig@netapp.com \
    --cc=Stuart.Lovett@netapp.com \
    --cc=Wendy.Peikes@netapp.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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