From: Hemlata Chelwani <chelwanihemlata@gmail.com>
To: Ankur Saini <arsenic.secondary@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 12.3 Released
Date: Wed, 10 May 2023 08:38:55 +0530 [thread overview]
Message-ID: <CAFT8bNNp-tv8UGib5exDhowDTUVbOOSgb16qFdnotmZn4zF-3Q@mail.gmail.com> (raw)
In-Reply-To: <356889C8-DFA5-49BA-8E92-38FF93B641E1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
Cool, thanks Ankur !
On Tue, 9 May 2023, 20:09 Ankur Saini, <arsenic.secondary@gmail.com> wrote:
> I think you can do that by via
>
> https://gcc.gnu.org/mailman/listinfo/gcc-announce
>
> > On 09-May-2023, at 7:34 PM, Hemlata Chelwani via Gcc <gcc@gcc.gnu.org>
> wrote:
> >
> > how can i unsubscribe ?
> > Best Regards,
> > Hemlata Chelwani
> >
> >
> > On Mon, 8 May 2023 at 18:52, Richard Biener via gcc-announce <
> > gcc-announce@gcc.gnu.org> wrote:
> >
> >> The GNU Compiler Collection version 12.3 has been released.
> >>
> >> GCC 12.3 is the first bug-fix release from the GCC 12 branch containing
> >> important fixes for regressions and serious bugs in GCC 12.2 with more
> >> than 127 bugs fixed since the previous release.
> >>
> >> This release is available from the WWW servers listed here:
> >>
> >> https://sourceware.org/pub/gcc/releases/gcc-12.3.0/
> >> https://gcc.gnu.org/mirrors.html
> >>
> >> Please do not contact me directly regarding questions or comments
> >> about this release. Instead, use the resources available from
> >> http://gcc.gnu.org.
> >>
> >> As always, a vast number of people contributed to this GCC release
> >> -- far too many to thank them individually!
> >>
>
>
prev parent reply other threads:[~2023-05-10 3:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 12:52 Richard Biener
2023-05-08 12:52 ` Richard Biener via gcc-announce
2023-05-09 14:04 ` Hemlata Chelwani
2023-05-09 14:39 ` Ankur Saini
2023-05-10 3:08 ` Hemlata Chelwani [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=CAFT8bNNp-tv8UGib5exDhowDTUVbOOSgb16qFdnotmZn4zF-3Q@mail.gmail.com \
--to=chelwanihemlata@gmail.com \
--cc=arsenic.secondary@gmail.com \
--cc=gcc@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).