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] Created tag 'glibc-2.37.9000' Date: Wed, 1 Feb 2023 03:41:28 +0000 (GMT) [thread overview] Message-ID: <20230201034128.B69843858D38@sourceware.org> (raw) The signed tag 'glibc-2.37.9000' was created pointing to: 2412deae1a... Open master branch for glibc 2.38 development Tagger: Carlos O'Donell <carlos@redhat.com> Date: Tue Jan 31 22:40:28 2023 -0500 Open master branch for glibc 2.38 development
reply other threads:[~2023-02-01 3:41 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=20230201034128.B69843858D38@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).