public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] Tag 2.30 release. Date: Thu, 01 Aug 2019 04:30:00 -0000 [thread overview] Message-ID: <20190801043013.13609.qmail@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0a8262a1b269f8f1602933248e69dfb041aab7a2 commit 0a8262a1b269f8f1602933248e69dfb041aab7a2 Author: Carlos O'Donell <carlos@redhat.com> Date: Thu Aug 1 00:29:13 2019 -0400 Tag 2.30 release. Diff: --- ChangeLog | 4 ++++ include/features.h | 2 +- version.h | 4 ++-- 3 files changed, 7 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index 9ddae24..cdb9e14 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,9 @@ 2019-08-01 Carlos O'Donell <carlos@redhat.com> + * version.h (RELEASE): Set to "stable". + (VERSION): Set to "2.30". + * include/features.h (__GLIBC_MINOR__): Set to 2.30. + * manual/install.texi: Update component versions. * INSTALL: Regenerate. * NEWS: Update. diff --git a/include/features.h b/include/features.h index e016b3e..bf47d88 100644 --- a/include/features.h +++ b/include/features.h @@ -439,7 +439,7 @@ /* Major and minor version number of the GNU C library package. Use these macros to test for features in specific releases. */ #define __GLIBC__ 2 -#define __GLIBC_MINOR__ 29 +#define __GLIBC_MINOR__ 30 #define __GLIBC_PREREQ(maj, min) \ ((__GLIBC__ << 16) + __GLIBC_MINOR__ >= ((maj) << 16) + (min)) diff --git a/version.h b/version.h index 40cfdcf..c2e25fc 100644 --- a/version.h +++ b/version.h @@ -1,4 +1,4 @@ /* This file just defines the current version number of libc. */ -#define RELEASE "development" -#define VERSION "2.29.9000" +#define RELEASE "stable" +#define VERSION "2.30"
reply other threads:[~2019-08-01 4:30 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190801043013.13609.qmail@sourceware.org \ --to=carlos@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).