From: Nick Clifton <nickc@sourceware.org>
To: bfd-cvs@sourceware.org, gdb-cvs@sourceware.org
Subject: [binutils-gdb] Created tag 'binutils-2_41-release'
Date: Wed, 2 Aug 2023 08:25:20 +0000 (GMT) [thread overview]
Message-ID: <20230802082520.BE1533858430@sourceware.org> (raw)
The unsigned tag 'binutils-2_41-release' was created pointing to:
675b9d612cc... 2.41 Release sources
Tagger: Nick Clifton <nickc@redhat.com>
Date: Wed Aug 2 09:23:50 2023 +0100
The GNU Binutils 2.41 release. (Please ignore the binutils-2_41 tag, it is wrong).
Diff:
Summary of changes (added commits):
-----------------------------------
675b9d6... 2.41 Release sources
reply other threads:[~2023-08-02 8:25 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=20230802082520.BE1533858430@sourceware.org \
--to=nickc@sourceware.org \
--cc=bfd-cvs@sourceware.org \
--cc=gdb-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).