public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Koenig <tkoenig@netcologne.de>
To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: Backports of foreign patches?
Date: Wed, 30 Dec 2020 10:52:48 +0100	[thread overview]
Message-ID: <5bc3cdf7-db6e-85d2-cf86-a16fa1756f2e@netcologne.de> (raw)
In-Reply-To: <trinity-59255846-425d-4ec3-959f-6121ed13224b-1609276869489@3c-app-gmx-bs48>

Hi Harald,

What I'm writing below is my personal opinion, if anybody feels
differently, please chime in.

 > just a hypothetical question: assume that some patch for a regression was
 > applied only to e.g. master some time ago but might be worth a backport,
 > the regression was indicated in the PR, and the patch author does not 
answer
 > any related queries in the PR?
 >
 > How could/should/would one proceed?
 >
 > Would it be acceptable to backport the patch after a sufficient 
waiting time
 > (at least e.g. one or two months)?

I would say yes.  Using "git gcc-backport" automatically credits
the original author, so that's OK.  Regarding the time frame, it
probably makes sense to backport before the next release of that
particular branch.

That is, if it does apply cleanly.  If there is some work needed
that exceeds being cosmetic, then this would in effect be a new
patch, which would require review.

 > With a notification to the ML?

Not needed if it applies cleanly.

 > Or does
 > it require an additional OK from a reviewer?

Only if it is a substantial rewrite (see above).

 > Or would one pass an invisible red line?

Certainly not for me - I would feel bad about not reacting
in the first place, but not about somebody backporting
one of my patches.

Best regards

     Thomas

  reply	other threads:[~2020-12-30  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 21:21 Harald Anlauf
2020-12-30  9:52 ` Thomas Koenig [this message]
2020-12-30 10:20   ` Paul Richard Thomas
     [not found] ` <0a216a6d-bbed-f5b7-dc8d-b430d80f2011@netcologne.de>
     [not found]   ` <trinity-6dfaef70-19a1-45d0-95c4-602532723b8d-1609326698125@3c-app-gmx-bs23>
2020-12-30 13:41     ` Fw: " 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=5bc3cdf7-db6e-85d2-cf86-a16fa1756f2e@netcologne.de \
    --to=tkoenig@netcologne.de \
    --cc=fortran@gcc.gnu.org \
    /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).