From: Harald Anlauf <anlauf@gmx.de>
To: Alexander Westbrooks <ctechnodev@gmail.com>
Cc: Jerry D <jvdelisle2@gmail.com>,
fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: PR82943 - Suggested patch to fix
Date: Sun, 21 Jan 2024 21:55:10 +0100 [thread overview]
Message-ID: <7da7ae53-d0a6-4ff7-9e26-8657469f6c50@gmx.de> (raw)
In-Reply-To: <CAGGSiqmFhj2mVMeMHPKrv_JY8dAJ_4Db-PiA9z-7nz6b1K==nw@mail.gmail.com>
Am 20.01.24 um 23:42 schrieb Alexander Westbrooks:
> Based on what I am reading here, I can either do the DCO path or the copy
> right form path? Or is it both, where I send in the copy right forms and
> then on every commit I put the DCO?
I thought the text is pretty clear. As already mentioned,
https://gcc.gnu.org/contribute.html#legal
gives you the options. One of these options is:
"Alternatively, a contributor can certify the Developer Certificate of
Origin for their contribution by adding the Signed-off-by: tag to their
submission."
If you opt for this variant,
https://gcc.gnu.org/dco.html
tells you everything. Basically (but please read yourself):
"The sign-off is a simple line at the end of the explanation for the
patch, which certifies that you wrote it or otherwise have the right to
pass it on as a free software patch. ..."
[...]
"then you just add a line saying:
Signed-off-by: Random J Developer <random@developer.example.org>
using your real name (sorry, no pseudonyms or anonymous contributions.) ..."
I think this would be sufficient.
>
> On Sat, Jan 20, 2024 at 3:40 PM Harald Anlauf <anlauf@gmx.de> wrote:
>
>> Am 20.01.24 um 21:37 schrieb Jerry D:
>>> On 1/20/24 12:08 PM, Harald Anlauf wrote:
>>>> Am 20.01.24 um 20:08 schrieb Jerry D:
>>>>> On 1/20/24 10:46 AM, Alexander Westbrooks wrote:
>>>>>> Hello and Happy New Year!
>>>>>>
>>>>>> I wanted to follow up on this patch I made to address PR82943 for
>>>>>> GFortran. Has anyone had a chance to review it?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Alexander Westbrooks
>>>>>>
>>>>>
>>>>> Inserting myself in here just a little bit. I will apply and test
>> today
>>>>> if I can. Paul is unavailable for a few weeks. Harald can chime in.
>>>>>
>>>>> Do you have commit rights for gcc?
>>>>
>>>> I am not aware of Alex having a copyright assignment on file,
>>>> or a DCO certificate, and the patch is not signed off.
>>>> But I might be wrong.
>>>>
>>> --- snip ---
>>>
>>> I do not mind committing this but need clarifications regarding the
>>> copyright (copyleft?) rules in this case. In the past we have allowed
>>> small contributions like this. This may be a little more than minor.
>>
>> It is. This is why I pointed to:
>>
>> https://gcc.gnu.org/dco.html
>>
>>> Regardless it appears to do the job!
>>>
>>> Jerry
>>>
>>>
>>
>>
>
prev parent reply other threads:[~2024-01-21 20:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 17:17 Alexander Westbrooks
2023-06-28 21:14 ` Harald Anlauf
2023-06-30 3:38 ` Alexander Westbrooks
2023-06-30 4:42 ` Steve Kargl
2023-06-30 6:40 ` Paul Richard Thomas
2023-06-30 9:08 ` Paul Richard Thomas
2023-07-17 15:56 ` Alexander Westbrooks
2024-01-20 18:46 ` Alexander Westbrooks
2024-01-20 19:08 ` Jerry D
2024-01-20 19:52 ` Jerry D
2024-01-20 20:08 ` Harald Anlauf
2024-01-20 20:37 ` Jerry D
2024-01-20 21:40 ` Harald Anlauf
2024-01-20 22:42 ` Alexander Westbrooks
2024-01-21 20:55 ` Harald Anlauf [this message]
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=7da7ae53-d0a6-4ff7-9e26-8657469f6c50@gmx.de \
--to=anlauf@gmx.de \
--cc=ctechnodev@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jvdelisle2@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).