public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/26868] Follow-up on x86-64 stub submission
Date: Mon, 10 May 2021 00:07:45 +0000	[thread overview]
Message-ID: <bug-26868-4717-qGcJmPJoDa@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26868-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26868

--- Comment #2 from Simon Marchi <simark at simark dot ca> ---
The last message I got from the FSF clerk was:

My apologies for the delays, but I now have what I need to proceed. I agree the
additional stub under the public domain makes sense. Fortunately, my opinions
don't count . It is up to you as maintainers! I'm just the clerk in this
process. The issue on my end was that contributors very rarely take the public
domain route, and I had difficulty finding examples that documented the
process; however, I did find an example, so I will move the process along as I
am able.

I'm not sure exactly what that means.  I guess we are good to go?  Do we still
need Caleb to have a copyright assignment?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-05-10  0:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-11 20:52 [Bug gdb/26868] New: " simark at simark dot ca
2020-11-11 20:52 ` [Bug gdb/26868] " simark at simark dot ca
2021-05-09 23:54 ` brobecker at gnat dot com
2021-05-10  0:07 ` simark at simark dot ca [this message]
2021-05-10 22:43 ` brobecker at gnat dot com
2021-05-30 14:05 ` brobecker at gnat dot com
2021-06-06 14:35 ` brobecker at gnat dot com
2024-01-05 14:03 ` ssbssa at sourceware dot org
2024-01-05 15:37 ` simon.marchi at polymtl dot ca
2024-01-10 18:41 ` tromey at sourceware dot org

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=bug-26868-4717-qGcJmPJoDa@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).