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] Open master branch for glibc 2.33 development. Date: Wed, 5 Aug 2020 03:43:55 +0000 (GMT) [thread overview] Message-ID: <20200805034355.233413858D37@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=4c56bcbceb05b44965d48e701711f850b83d7c69 commit 4c56bcbceb05b44965d48e701711f850b83d7c69 Author: Carlos O'Donell <carlos@redhat.com> Date: Tue Aug 4 23:41:43 2020 -0400 Open master branch for glibc 2.33 development. Happy hacking! Diff: --- NEWS | 24 ++++++++++++++++++++++++ version.h | 4 ++-- 2 files changed, 26 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 485b8ddffa..2937adc3f3 100644 --- a/NEWS +++ b/NEWS @@ -4,6 +4,30 @@ See the end for copying conditions. Please send GNU C library bug reports via <https://sourceware.org/bugzilla/> using `glibc' in the "product" field. +\f +Version 2.33 + +Major new features: + + [Add new features here] + +Deprecated and removed features, and other changes affecting compatibility: + + [Add deprecations, removals and changes affecting compatibility here] + +Changes to build and runtime requirements: + + [Add changes to build and runtime requirements here] + +Security related changes: + + [Add security related changes here] + +The following bugs are resolved with this release: + + [The release manager will add the list generated by + scripts/list-fixed-bugs.py just before the release.] + \f Version 2.32 diff --git a/version.h b/version.h index 83cd196798..0fe0b6bf5c 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 VERSION "2.32" +#define RELEASE "development" +#define VERSION "2.32.9000"
reply other threads:[~2020-08-05 3:43 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=20200805034355.233413858D37@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).