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: Tom Tromey <tom@tromey.com>,
	"H.J. Lu via Binutils" <binutils@sourceware.org>
Subject: Re: 2.36 Branch imminent
Date: Tue, 5 Jan 2021 14:55:47 -0800	[thread overview]
Message-ID: <CAMe9rOrN7E45vj8Ko14OzCttmNkazw+0qbvNczBLO7MPcbVvgA@mail.gmail.com> (raw)
In-Reply-To: <fa7587fa-9f1f-e7a0-403e-facf61d62401@redhat.com>

On Tue, Jan 5, 2021 at 2:50 AM Nick Clifton <nickc@redhat.com> wrote:
>
> Hi H.J.
>
> >>>> https://sourceware.org/pipermail/gdb-patches/2020-December/174120.html
>
> Where are we with testing of this patch for other projects ?
>
> I think that I saw a problem report from a gdb developer fly by, but
> I may have been mistaken.
>

I got no feedbacks for my current patch set:

https://sourceware.org/pipermail/gdb-patches/2020-December/174216.html


-- 
H.J.

  reply	other threads:[~2021-01-05 22:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14 11:44 Nick Clifton
2020-12-14 11:48 ` H.J. Lu
2020-12-14 12:45   ` Nick Clifton
2020-12-15 13:32 ` H.J. Lu
2020-12-15 13:51   ` Nick Clifton
2020-12-15 13:57     ` H.J. Lu
2020-12-15 17:00       ` Nick Clifton
2020-12-15 17:15       ` Tom Tromey
2020-12-15 17:25         ` H.J. Lu
2020-12-15 17:33           ` Tom Tromey
2020-12-15 18:25             ` H.J. Lu
2021-01-05 10:50               ` Nick Clifton
2021-01-05 22:55                 ` H.J. Lu [this message]
2021-01-07 12:10                   ` Nick Clifton
2021-01-09 14:37                     ` Support the PGO build for binutils+gdb (2.36 Branch imminent) H.J. Lu
2021-01-13 12:47           ` 2.36 Branch imminent Pedro Alves
2021-01-06  7:51 ` Kyrylo Tkachov

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=CAMe9rOrN7E45vj8Ko14OzCttmNkazw+0qbvNczBLO7MPcbVvgA@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    --cc=tom@tromey.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).