public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.com>
To: Nick Clifton <nickc@redhat.com>, Binutils <binutils@sourceware.org>
Cc: YunQiang Su <syq@debian.org>,
	"debian-mips@lists.debian.org" <debian-mips@lists.debian.org>
Subject: Re: 2.39 Release Schedule
Date: Mon, 27 Jun 2022 20:43:46 +0200	[thread overview]
Message-ID: <b8ee3d42-bfcb-b9a4-d1e2-1091c90da66d@ubuntu.com> (raw)
In-Reply-To: <9e7bc498-5598-baaa-3b40-001aa7e772a8@redhat.com>

On 27.06.22 13:37, Nick Clifton via Binutils wrote:
> Hi Guys,
> 
>    OK, so the plan is that the branch for the 2.39 release will be
>    cut on Friday July 8th (just before I go on vacation).  All being
>    well the release itself will happen in the first weekend of August
>    (Sat 6th probably).
> 
>    If you have new features that you want to get into the 2.39 release
>    now is the time to submit them - or ping for a review if they have
>    already been submitted.
> 
>    Once the branch is cut the usual rules will apply - bug fixes and
>    doc updates only - although this time around I am also going to ask
>    that any maintainer who wishes to do so review and approve/reject
>    patches for the branch.
> 
>    I will be away July 11..July 22 but as soon as I get back I will be
>    on patch review duty for as much of the time as I can.

with today's trunk, I see regressions on i686-linux-gnu and mips64el-linux-gnu:

i386:
W: [ld-elf/elf.exp] REGRESSION (UNSUPPORTED -> FAIL): static init array mixed

trunk 20220622 didn't show that.

mips64el:
I: [binutils-all/objcopy.exp] progression (UNTESTED -> PASS): simple objcopy of 
executable
I: [binutils-all/objcopy.exp] progression (UNTESTED -> PASS): run objcopy of 
executable
I: [binutils-all/objcopy.exp] progression (UNTESTED -> PASS): run stripped 
executable
I: [binutils-all/objcopy.exp] progression (UNTESTED -> PASS): run stripped 
executable with saving a symbol
I: [binutils-all/objcopy.exp] progression (UNTESTED -> PASS): keep only debug data
I: [binutils-all/objcopy.exp] progression (UNTESTED -> PASS): simple objcopy of 
debug data
I: [binutils-all/objcopy.exp] progression (UNTESTED -> PASS): NOBITS sections 
retain sh_link field
W: [ld-elf/elf.exp] REGRESSION (PASS -> FAIL): PR ld/29072 (warn about an 
executable .note.GNU-stack)

trunk 20220622 also didn't show that.

  reply	other threads:[~2022-06-27 18:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 11:37 Nick Clifton
2022-06-27 18:43 ` Matthias Klose [this message]
2022-06-28  1:03   ` Alan Modra
2022-07-01  4:08 ` Matthias Klose

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=b8ee3d42-bfcb-b9a4-d1e2-1091c90da66d@ubuntu.com \
    --to=doko@ubuntu.com \
    --cc=binutils@sourceware.org \
    --cc=debian-mips@lists.debian.org \
    --cc=nickc@redhat.com \
    --cc=syq@debian.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).