public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexander Westbrooks <ctechnodev@gmail.com>
To: Harald Anlauf <anlauf@gmx.de>
Cc: Jerry D <jvdelisle2@gmail.com>,
	fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: PR82943 - Suggested patch to fix
Date: Sat, 20 Jan 2024 16:42:10 -0600	[thread overview]
Message-ID: <CAGGSiqmFhj2mVMeMHPKrv_JY8dAJ_4Db-PiA9z-7nz6b1K==nw@mail.gmail.com> (raw)
In-Reply-To: <38ddc722-9806-4dad-911d-3d47e971284f@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1471 bytes --]

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?

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
> >
> >
>
>

  parent reply	other threads:[~2024-01-20 22:42 UTC|newest]

Thread overview: 19+ 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-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:08           ` Harald Anlauf
2024-01-20 20:37           ` Jerry D
2024-01-20 21:40             ` Harald Anlauf
2024-01-20 21:40               ` Harald Anlauf
2024-01-20 22:42               ` Alexander Westbrooks [this message]
2024-01-21 20:55                 ` Harald Anlauf
2024-01-21 20:55                   ` Harald Anlauf

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='CAGGSiqmFhj2mVMeMHPKrv_JY8dAJ_4Db-PiA9z-7nz6b1K==nw@mail.gmail.com' \
    --to=ctechnodev@gmail.com \
    --cc=anlauf@gmx.de \
    --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).