From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Guinevere Larsen <blarsen@redhat.com>,
pinskia@gmail.com, gdb@sourceware.org, binutils@sourceware.org
Subject: Re: DCO: Was: Re: Contributing to gdb
Date: Thu, 27 Jun 2024 14:48:00 -0300 [thread overview]
Message-ID: <871q4iffan.fsf@linaro.org> (raw)
In-Reply-To: <86ed8uqvyw.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 18 Jun 2024 15:25:11 +0300")
Hello Eli,
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Mon, 17 Jun 2024 16:48:13 -0300
>> Cc: pinskia@gmail.com, gdb@sourceware.org, binutils@sourceware.org
>> From: Guinevere Larsen <blarsen@redhat.com>
>>
> This must be some grave misunderstanding. The discussion to which I
> pointed was a very long one, took more than a month, and expecting me
> (or someone else) to summarize it is unreasonable, even if you ignore
> the possibility that a summary might omit aspects that are important
> for you, let alone the time required to produce such a summary. The
> gnu-prog-discuss list had a very small number of threads in June 2021,
> so I thought finding the right one would be a no-brainer. But since
> it sounds like I was mistaken, I apologize; here's the link to the
> beginning of that thread:
>
> https://lists.gnu.org/mailman/private/gnu-prog-discuss/2021q2/016757.html
>
> The subject of the thread is, unsurprisingly, "Copyright assignments".
> It also points to related discussions on GCC, glibc, and Gnulib lists.
>
> The reason I think a serious discussion of this should start by
> reading that one is that it doesn't sound a good investment of
> everyone's time to re-iterate all the arguments which were already
> brought forward there and discussed from every possible aspect. I
> apologize for not making myself clear earlier, and hope I made myself
> more clear now: there was no intent to be unhelpful, just an attempt
> to be efficient by pointing to a very extensive discussion of this and
> related topics.
I'm interested in reading that thread and in the discussion of whether
GDB should accept contributions under the DCO. I don't have a personal
need for it, but my opinion is that it would be beneficial to the GDB
project.
Unfortunately I can't access that mailing list archive: it requires a
password. My understanding is that gnu-prog-discuss is only accessible
to GNU project maintainers.
Would it be possible to copy that mailing list thread to a publicly
accessible location?
--
Thiago
next prev parent reply other threads:[~2024-06-27 17:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 21:52 shaunak saha
2024-06-17 12:21 ` Guinevere Larsen
2024-06-17 15:00 ` DCO: Was: " Andrew Pinski
2024-06-17 15:57 ` Guinevere Larsen
2024-06-17 16:07 ` Jan Beulich
2024-06-17 16:32 ` Eli Zaretskii
2024-06-17 16:37 ` Guinevere Larsen
2024-06-17 16:45 ` Eli Zaretskii
2024-06-17 18:18 ` Guinevere Larsen
2024-06-17 18:24 ` Andrew Pinski
2024-06-17 19:57 ` Eli Zaretskii
2024-06-17 19:37 ` Eli Zaretskii
2024-06-17 19:48 ` Guinevere Larsen
2024-06-18 12:25 ` Eli Zaretskii
2024-06-27 17:48 ` Thiago Jung Bauermann [this message]
2024-06-27 19:03 ` Eli Zaretskii
2024-06-29 3:27 ` Thiago Jung Bauermann
2024-06-17 19:15 ` Arsen Arsenović
2024-06-18 11:54 ` Eli Zaretskii
2024-06-28 0:43 ` NightStrike
2024-06-28 6:08 ` Eli Zaretskii
2024-06-21 13:20 ` Nick Clifton
2024-06-23 22:06 ` Tom Tromey
2024-06-18 13:32 ` Michael Matz
2024-06-19 7:38 ` shaunak saha
2024-06-19 12:07 ` Guinevere Larsen
2024-06-25 22:27 ` shaunak saha
2024-06-26 17:38 ` Tom Tromey
2024-06-28 7:23 ` shaunak saha
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=871q4iffan.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=binutils@sourceware.org \
--cc=blarsen@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=pinskia@gmail.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).