public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Harald Anlauf <anlauf@gmx.de>
To: fortran <fortran@gcc.gnu.org>
Subject: Fw: Re: Backports of foreign patches?
Date: Wed, 30 Dec 2020 14:41:07 +0100	[thread overview]
Message-ID: <trinity-ea873948-e9a0-483c-824e-086cf0ace2f0-1609335667849@3c-app-gmx-bap67> (raw)
In-Reply-To: <trinity-6dfaef70-19a1-45d0-95c4-602532723b8d-1609326698125@3c-app-gmx-bs23>

I'm forwarding this to the ML, as I did not pay sufficient attention
to the distribution list...

> Gesendet: Mittwoch, 30. Dezember 2020 um 12:11 Uhr
> Von: "Harald Anlauf"
> An: "Thomas Koenig"
> Betreff: Re: Backports of foreign patches?
>
> Hi Thomas, Paul,
>
> thanks for the clear statements.
>
> I am less concerned about what I have at home than what
> I might have supported at work say two or three years from now.
>
> We now have ("just got")
>
> % cat /etc/redhat-release
> Red Hat Enterprise Linux ComputeNode release 7.7 (Maipo)
>
> which has a baseline of
>
> gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39)
>
> but for real work also have an installed module with 9.1.0.
> Expectations might be more realistic for a higher minor version
> than for a higher major version...
>
> Best regards,
> Harald
>

      parent reply	other threads:[~2020-12-30 13:41 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
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     ` 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=trinity-ea873948-e9a0-483c-824e-086cf0ace2f0-1609335667849@3c-app-gmx-bap67 \
    --to=anlauf@gmx.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).