public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "MIAH, Shahad" <shahad.miah@airbus.com>
To: Florian Weimer <fweimer@redhat.com>,
	"MIAH, Shahad via Gcc-help" <gcc-help@gcc.gnu.org>
Subject: RE: GnuPG & GNU GCC Compiler
Date: Wed, 3 May 2023 09:42:50 +0000	[thread overview]
Message-ID: <9f6dff066c884a1a8f8829a1ec417e8e@CD1-4DDAG01-P02.cdmail.common.airbusds.corp> (raw)
In-Reply-To: <87cz3o8gpb.fsf@oldenburg.str.redhat.com>

&nbsp;
Morning Florian,

Thank you for your email and apologies for the delay in replying back to your email. Thank you for that information, I will now pass this over to our relevant team who deals with these applications and will advise on upgrading to the latest version.

Kind Regards
Shahad Miah
IT Service Operation
TDBES Functional and SW Design department
Airbus Defence and Space
Gunnels Wood Road
Stevenage
Hertfordshire SG1 2AS
United Kingdom
T:  +44 1438 773580
M: +44 7795 930835
E: shahad.miah@airbus.com / shahad.miah@uk.airbus.com





THIS DOCUMENT IS NOT SUBJECT TO EXPORT CONTROL.

-----Original Message-----
From: Florian Weimer [mailto:fweimer@redhat.com] 
Sent: Friday, April 28, 2023 11:06 AM
To: MIAH, Shahad via Gcc-help <gcc-help@gcc.gnu.org>
Cc: MIAH, Shahad <shahad.miah@airbus.com>
Subject: Re: GnuPG & GNU GCC Compiler

* Shahad via Gcc-help MIAH:

> My employer are currently using following application: GnuPG version
> 4.0 & GNU GCC Compiler version 1.0 and we are in the process of 
> reviewing all our desktop applications therefore we would like to know 
> if this version is still be supported with patches and security 
> updates? and if so can you please advise when will this support end?

If you mean GCC 4.0 and GnuPG 1.0, these versions are very old.  I doubt you will be able to find commercial support for them at this point.  The upstream projects definitely have moved on.  The last commit to the GCC
4.0 branch not related to release engineering was in January 2007.

You also need to check if ongoing upstream maintenance statisfies your needs, or if you need support from an internal team or a commercial vendor (usually it's one of the latter two).

Thanks,
Florian

This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Airbus Defence and Space Limited disclaims any and all liability if this email transmission was virus corrupted, altered or falsified.
-o-
Emails to Airbus Defence and Space Limited may be processed, recorded and monitored outside the UK.
-o-
Airbus Defence and Space Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England


      reply	other threads:[~2023-05-03  9:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28  9:42 MIAH, Shahad
2023-04-28 10:05 ` Florian Weimer
2023-05-03  9:42   ` MIAH, Shahad [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=9f6dff066c884a1a8f8829a1ec417e8e@CD1-4DDAG01-P02.cdmail.common.airbusds.corp \
    --to=shahad.miah@airbus.com \
    --cc=fweimer@redhat.com \
    --cc=gcc-help@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).