From: Eli Zaretskii via Gdb <gdb@sourceware.org>
To: Guinevere Larsen <blarsen@redhat.com>
Cc: pinskia@gmail.com, gdb@sourceware.org, binutils@sourceware.org
Subject: Re: DCO: Was: Re: Contributing to gdb
Date: Tue, 18 Jun 2024 15:25:11 +0300 [thread overview]
Message-ID: <86ed8uqvyw.fsf@gnu.org> (raw)
In-Reply-To: <df781632-9f3c-4893-9769-e153ab90c37a@redhat.com> (message from Guinevere Larsen on Mon, 17 Jun 2024 16:48:13 -0300)
> 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>
>
> On 6/17/24 4:37 PM, Eli Zaretskii wrote:
> > That's not an excuse. And you can ask me to do that. I will make
> > time for it, exactly as I make time to review documentation patches
> > here, and as I make time to explain this stuff to contributors to
> > Emacs.
>
> Then I suggest you add your name and email to the wiki, where the people
> that never even get to the point of interacting with us will find it to
> ask for questions.
>
> https://sourceware.org/gdb/wiki/ContributionChecklist#FSF_copyright_Assignment
I don't mind, but I didn't see any names and emails mentioned there.
Did I miss something?
> > Anyone who wants to discuss this seriously should first read the
> > gnu-prog-discuss discussion of these issues, from June 2021 (it went
> > on all the way through July).
> >
> Telling someone who actively asked to learn more that "ok, go read those
> email threads" without any convenience like saying the subject to search
> for it easily, or the archive where I can look for it, and furthermore,
> I am forced to subscribe to a list I frankly do not care about just to
> see the discussion you consider required reading before even accepting
> to have a conversation is a very unhelpful way to explain anything for
> anyone.
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.
next prev parent reply other threads:[~2024-06-18 12:26 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 21:52 shaunak saha via Gdb
2024-06-17 12:21 ` Guinevere Larsen via Gdb
2024-06-17 15:00 ` DCO: Was: " Andrew Pinski via Gdb
2024-06-17 15:57 ` Guinevere Larsen via Gdb
2024-06-17 16:07 ` Jan Beulich via Gdb
2024-06-17 16:32 ` Eli Zaretskii via Gdb
2024-06-17 16:37 ` Guinevere Larsen via Gdb
2024-06-17 16:45 ` Eli Zaretskii via Gdb
2024-06-17 18:18 ` Guinevere Larsen via Gdb
2024-06-17 18:24 ` Andrew Pinski via Gdb
2024-06-17 19:57 ` Eli Zaretskii via Gdb
2024-06-17 19:37 ` Eli Zaretskii via Gdb
2024-06-17 19:48 ` Guinevere Larsen via Gdb
2024-06-18 12:25 ` Eli Zaretskii via Gdb [this message]
2024-06-27 17:48 ` Thiago Jung Bauermann via Gdb
2024-06-27 19:03 ` Eli Zaretskii via Gdb
2024-06-29 3:27 ` Thiago Jung Bauermann via Gdb
2024-06-17 19:15 ` Arsen Arsenović via Gdb
2024-06-18 11:54 ` Eli Zaretskii via Gdb
2024-06-28 0:43 ` NightStrike via Gdb
2024-06-28 6:08 ` Eli Zaretskii via Gdb
2024-06-21 13:20 ` Nick Clifton via Gdb
2024-06-23 22:06 ` Tom Tromey
2024-12-02 8:56 ` Luis Machado via Gdb
2025-01-13 17:14 ` Andrew Burgess via Gdb
2025-01-13 17:32 ` Eli Zaretskii via Gdb
2025-01-17 10:37 ` Florian Weimer via Gdb
2025-01-17 10:44 ` Luis Machado via Gdb
2025-01-17 13:01 ` Eli Zaretskii via Gdb
2025-01-21 19:10 ` Guinevere Larsen via Gdb
2025-01-13 17:42 ` Simon Marchi via Gdb
2025-01-14 15:17 ` automated coding style tool (was: RE: DCO: Was: Re: Contributing to gdb) Aktemur, Tankut Baris via Gdb
2025-01-14 17:11 ` automated coding style tool Tom Tromey
2025-01-14 17:14 ` Luis Machado via Gdb
2025-01-14 17:23 ` Simon Marchi via Gdb
2025-01-14 23:04 ` Tom Tromey
2025-01-15 6:03 ` Maciej W. Rozycki
2025-01-18 18:39 ` Tom Tromey
2025-01-22 22:36 ` Maciej W. Rozycki
2025-01-15 10:20 ` Luis Machado via Gdb
2025-01-15 12:24 ` Aktemur, Tankut Baris via Gdb
2025-01-17 13:42 ` Andrew Burgess via Gdb
2025-01-17 15:13 ` Joel Brobecker via Gdb
2025-01-17 15:55 ` Simon Marchi via Gdb
2025-01-17 17:36 ` Phi via Gdb
2025-01-17 19:27 ` Simon Marchi via Gdb
2025-01-18 18:56 ` Tom Tromey
2025-01-20 11:30 ` Luis Machado via Gdb
2025-01-14 17:15 ` Simon Marchi via Gdb
2025-01-14 9:49 ` DCO: Was: Re: Contributing to gdb Luis Machado via Gdb
2025-01-14 13:56 ` Eli Zaretskii via Gdb
2025-01-14 15:10 ` Simon Marchi via Gdb
2025-01-14 15:28 ` Luis Machado via Gdb
2025-01-14 15:47 ` Simon Marchi via Gdb
2025-01-14 16:33 ` Luis Machado via Gdb
2025-01-14 16:42 ` Eli Zaretskii via Gdb
2025-01-15 11:49 ` Mark Wielaard
2025-01-14 16:46 ` Andrew Burgess via Gdb
2025-01-15 11:25 ` Mark Wielaard
2025-01-15 6:20 ` Maciej W. Rozycki
2025-01-15 11:05 ` Mark Wielaard
2025-01-14 15:28 ` Mark Wielaard
2025-01-17 10:42 ` Florian Weimer via Gdb
2025-01-17 13:09 ` Eli Zaretskii via Gdb
2025-01-19 16:37 ` Mark Wielaard
2025-01-27 15:55 ` DCO Bradley M. Kuhn via Gdb
2025-01-27 16:36 ` DCO Krzysztof Siewicz via Gdb
2025-01-27 17:22 ` DCO Guinevere Larsen via Gdb
2025-01-31 19:36 ` DCO Mark Wielaard
2024-06-18 13:32 ` DCO: Was: Re: Contributing to gdb Michael Matz via Gdb
2024-06-19 7:38 ` shaunak saha via Gdb
2024-06-19 12:07 ` Guinevere Larsen via Gdb
2024-06-25 22:27 ` shaunak saha via Gdb
2024-06-26 17:38 ` Tom Tromey
2024-06-28 7:23 ` shaunak saha via Gdb
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=86ed8uqvyw.fsf@gnu.org \
--to=gdb@sourceware.org \
--cc=binutils@sourceware.org \
--cc=blarsen@redhat.com \
--cc=eliz@gnu.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