[Bug gdb/26868] New: Follow-up on x86-64 stub submission

[Bug gdb/26868] New: Follow-up on x86-64 stub submission

[simark at simark dot ca]

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

            Bug ID: 26868
           Summary: Follow-up on x86-64 stub submission
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: simark at simark dot ca
  Target Milestone: ---

Before branching (or at least releasing) GDB 11, follow-up on this.  We are
currently waiting for a response from the FSF about the license to use (same as
the rest of GDB, or public domain like the other stubs).  Caleb is also waiting
for a response to the copyright assignment form.

https://sourceware.org/pipermail/gdb-patches/2020-November/173182.html

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

[Bug gdb/26868] Follow-up on x86-64 stub submission

[simark at simark dot ca]

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

Simon Marchi <simark at simark dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |11.1

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

[Bug gdb/26868] Follow-up on x86-64 stub submission

[brobecker at gnat dot com]

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

Joel Brobecker <brobecker at gnat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |brobecker at gnat dot com

--- Comment #1 from Joel Brobecker <brobecker at gnat dot com> ---
Hi Simon.

Quick update: I dont' seem to be able to find Caleb in the FSF files of people
who have assigned copyright. Do you happen to know whether the copyright
assignment has gone through, since then?

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

[Bug gdb/26868] Follow-up on x86-64 stub submission

[simark at simark dot ca]

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.

[Bug gdb/26868] Follow-up on x86-64 stub submission

[brobecker at gnat dot com]

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

--- Comment #3 from Joel Brobecker <brobecker at gnat dot com> ---
The way I read it is that the FSF is not ready to answer our question and that
it is asking us to make the decision, knowing that we are even less equipped
than the FSF to do so :-/.

The main question is whether we can consider that this contribution is either
in the public domain, or falls within the "obvious change" or "tiny change"
allowance.

For the code to be public domain, Caleb would need to disclaim it, and he
unfortunately cannot do so by email. The FSF has a disclaim form for that very
purpose. Also, since Caleb appears to be working for NetApp IIUC, if the code
was written as part of his work, it's actually his employer that would need to
disclaim it.

As for the "obvious" or "tiny" rule, I did a diff between gdb/stub/i386-stub.c
and the proposed x86_64-stub.c, and besides the changes that are pure
formatting or documentation, I think there are a sufficient number of changes
that I think it would be hard to argue that the change is either "obvious" or
"tiny".

So, I'm afraid in this case that we can't take this contribution without an
assignment on file, either pure disclaim putting the code in the public domain,
or assigning the copyright to the FSF.

I'm not a lawyer, so I might be off in my understanding, but I think we should
even more careful with these questions when not sure...

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

[Bug gdb/26868] Follow-up on x86-64 stub submission

[brobecker at gnat dot com]

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

--- Comment #4 from Joel Brobecker <brobecker at gnat dot com> ---
Do we want to close this PR, or do we want to try to pursue the copyright
assignment issue a bit more?

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

[Bug gdb/26868] Follow-up on x86-64 stub submission

[brobecker at gnat dot com]

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

Joel Brobecker <brobecker at gnat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|11.1                        |---

--- Comment #5 from Joel Brobecker <brobecker at gnat dot com> ---
> Do we want to close this PR, or do we want to try to pursue the copyright
> assignment issue a bit more?

I'm going to start by removing the 11.1 Target Milestone. I think we tried our
best to remember to handle this in time for the GDB 11 release, but this is
otherwise not release-critical. I'm not opposed to delaying the release by a
week or two if there is an effort from the patch's author to assign the
copyright to the FSF, though.

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

[Bug gdb/26868] Follow-up on x86-64 stub submission

[ssbssa at sourceware dot org]

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

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ssbssa at sourceware dot org

--- Comment #6 from Hannes Domani <ssbssa at sourceware dot org> ---
Is there still something to be done here?

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

[Bug gdb/26868] Follow-up on x86-64 stub submission

[simon.marchi at polymtl dot ca]

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

Simon Marchi <simon.marchi at polymtl dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simon.marchi at polymtl dot ca

--- Comment #7 from Simon Marchi <simon.marchi at polymtl dot ca> ---
Here's the thread on public inbox, it's easier to read:
https://inbox.sourceware.org/gdb-patches/fcc7109f-a6d9-bbd3-6e09-10a75c09887a@simark.ca/

We never heard back from Caleb regarding the copyright assignment, so right now
there's nothing we can do.  If there's no plan to follow up on this, I think we
can close the bug (the code can still be merged in the future if the copyright
assignment issue gets resolved).

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

[Bug gdb/26868] Follow-up on x86-64 stub submission

[tromey at sourceware dot org]

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

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #8 from Tom Tromey <tromey at sourceware dot org> ---
Closing for now.

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