public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: GNU Binutils 2.41 release
Date: Fri, 4 Aug 2023 11:02:55 -0700	[thread overview]
Message-ID: <CAMe9rOqx11deZeHJiB8=3WUCWU-=W5VUx-jDTM3Rrt04GM9aag@mail.gmail.com> (raw)
In-Reply-To: <f65361b7-573f-bd1a-ba4c-9b0cf4367adc@redhat.com>

On Fri, Aug 4, 2023 at 3:37 AM Nick Clifton <nickc@redhat.com> wrote:
>
> Hi Guys,
>
> On 7/31/23 18:25, H.J. Lu wrote:
> > The binutils-2_41 tag points to the wrong commit:
>
> Indeed it does.  In fact there was no commit that exactly corresponds to
> the released sources.  A silly mistake on my part.
>
> After some trial and error we now have a new branch (binutils-2_41-release-point)
> and a new tag (binutils-2_41-official-release), that is a match for the released
> sources.
>
> There are no plans to ever make any changes to this branch - it is just there
> so that we can have a tag that matches the release.
>
> I will update the website to mention this problem, and I apologise
> to anyone who has been caught out by the mis-tagging.
>

Thanks.


-- 
H.J.

  reply	other threads:[~2023-08-04 18:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-30 14:57 Nick Clifton
2023-07-31 17:25 ` H.J. Lu
2023-08-01  9:43   ` Nick Clifton
2023-08-01 10:15     ` Tsukasa OI
2023-08-04 10:37   ` Nick Clifton
2023-08-04 18:02     ` H.J. Lu [this message]
2023-08-04 19:57 ` ASSI
2023-08-05  0:38   ` Sam James
2023-08-05 10:08     ` ASSI
2023-08-06  3:00     ` Tsukasa OI

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='CAMe9rOqx11deZeHJiB8=3WUCWU-=W5VUx-jDTM3Rrt04GM9aag@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    /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).