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] Prepare for glibc 2.36 release.
Date: Fri, 29 Jul 2022 21:59:41 +0000 (GMT)	[thread overview]
Message-ID: <20220729215941.171BB385AC32@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=f94b70bd3a3d0c9c6f17b272b61b345f4f6cbfbe

commit f94b70bd3a3d0c9c6f17b272b61b345f4f6cbfbe
Author: Carlos O'Donell <carlos@redhat.com>
Date:   Fri Jul 29 17:59:01 2022 -0400

    Prepare for glibc 2.36 release.
    
    Update version.h, and include/features.h.

Diff:
---
 include/features.h | 2 +-
 version.h          | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/include/features.h b/include/features.h
index 76b8b973d4..123de9fd47 100644
--- a/include/features.h
+++ b/include/features.h
@@ -479,7 +479,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__	35
+#define	__GLIBC_MINOR__	36
 
 #define __GLIBC_PREREQ(maj, min) \
 	((__GLIBC__ << 16) + __GLIBC_MINOR__ >= ((maj) << 16) + (min))
diff --git a/version.h b/version.h
index e27a39e149..e211fb4441 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.35.9000"
+#define RELEASE "stable"
+#define VERSION "2.36"


                 reply	other threads:[~2022-07-29 21:59 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=20220729215941.171BB385AC32@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: 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).