From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: GDB 9.0.90 available for testing
Date: Fri, 17 Jan 2020 20:56:00 -0000 [thread overview]
Message-ID: <CAPTJ0XFVFkrAPvkuGYxtQJCXmvYu5eGe7-nvkABqXTL3-jEo-A@mail.gmail.com> (raw)
In-Reply-To: <83h81pwxkb.fsf@gnu.org>
On Tue, Dec 24, 2019 at 10:30 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Date: Tue, 24 Dec 2019 07:53:15 +0400
> > From: Joel Brobecker <brobecker@adacore.com>
> > Cc: cbiesinger@google.com, gdb-patches@sourceware.org
> >
> > > > - Keep track of the patch submission on the readline end;
> > >
> > > How does one do that? I looked at the Readline's Git repository, but
> > > couldn't find the patch there, and didn't understand the branch
> > > arrangement. Perhaps Chet didn't yet push the changes? Or am I
> > > missing something?
> >
> > That one is a little tougher. When I read Chet's message, I thought
> > it was a little ambiguous, but the way I read it was that he was
> > only acknowledging the receipt of the report and patch, so he hadn't
> > had a chance to review and apply it. What I would do is ask him
> > if he could let us know when it is reviewed and (hopefully) applied.
> >
> > If he forgets, that's not a huge deal, but we basically expose
> > ourselves to facing that same issue again at the next readline
> > upgrade. We could be even more proactive, but I don't think it
> > would be worth the effort.
>
> OK, thanks. I will try to keep an eye on Readline.
Looks like this landed in readline:
http://git.savannah.gnu.org/cgit/readline.git/diff/posixstat.h?h=devel&id=e09431eaf2de3c3ac289a42c85a760ec549f634e
I haven't checked if there are any changes relative to Eli's patch.
Christian
next prev parent reply other threads:[~2020-01-17 20:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 21:47 Joel Brobecker
2019-12-11 21:56 ` Joel Brobecker
2019-12-16 17:23 ` Eli Zaretskii
2019-12-16 17:38 ` Simon Marchi
2019-12-16 17:50 ` Eli Zaretskii
2019-12-23 7:54 ` Joel Brobecker
2019-12-16 18:52 ` Christian Biesinger via gdb-patches
2019-12-16 19:18 ` Eli Zaretskii
2019-12-16 19:36 ` Pedro Alves
2019-12-16 19:57 ` Eli Zaretskii
2019-12-16 20:37 ` Christian Biesinger via gdb-patches
2019-12-16 20:38 ` Pedro Alves
2019-12-17 17:25 ` Eli Zaretskii
2019-12-18 20:19 ` Christian Biesinger via gdb-patches
2019-12-19 15:00 ` Eli Zaretskii
2019-12-19 19:17 ` Christian Biesinger via gdb-patches
2019-12-19 19:38 ` Eli Zaretskii
2019-12-23 7:43 ` Joel Brobecker
2019-12-23 17:32 ` Eli Zaretskii
2019-12-24 3:53 ` Joel Brobecker
2019-12-24 15:30 ` Eli Zaretskii
2020-01-17 20:56 ` Christian Biesinger via gdb-patches [this message]
2020-01-17 21:09 ` Eli Zaretskii
2019-12-23 8:01 ` Joel Brobecker
2019-12-23 13:56 ` Eli Zaretskii
2019-12-24 3:49 ` Joel Brobecker
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=CAPTJ0XFVFkrAPvkuGYxtQJCXmvYu5eGe7-nvkABqXTL3-jEo-A@mail.gmail.com \
--to=gdb-patches@sourceware.org \
--cc=brobecker@adacore.com \
--cc=cbiesinger@google.com \
--cc=eliz@gnu.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).