From: Carlos O'Donell <carlos@redhat.com>
To: libc-stable@sourceware.org
Subject: Re: [PATCH] Set version.h RELEASE to "stable".
Date: Fri, 2 Oct 2020 15:35:34 -0400 [thread overview]
Message-ID: <0df8b85a-6856-d066-dc2c-21c30d8157d7@redhat.com> (raw)
In-Reply-To: <20201002193330.1698018-1-carlos@redhat.com>
On 10/2/20 3:33 PM, Carlos O'Donell wrote:
> The RELEASE macro was accidentaly set to "release" instead of
> the expected "stable" by the release manager. This is a mistake
> that leads to the build using "-g -O1" instead of "-g -O2" if
> configure was executed with "CFLAGS=" (CFLAGS set but empty).
> ---
> version.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/version.h b/version.h
> index 83cd196798..e6ca7a8857 100644
> --- a/version.h
> +++ b/version.h
> @@ -1,4 +1,4 @@
> /* This file just defines the current version number of libc. */
>
> -#define RELEASE "release"
> +#define RELEASE "stable"
> #define VERSION "2.32"
>
Needs a bug number in the commit message. Fixing that up.
--
Cheers,
Carlos.
prev parent reply other threads:[~2020-10-02 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 19:33 Carlos O'Donell
2020-10-02 19:35 ` Carlos O'Donell [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=0df8b85a-6856-d066-dc2c-21c30d8157d7@redhat.com \
--to=carlos@redhat.com \
--cc=libc-stable@sourceware.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).