Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 10 branching - 2020-07-18 Update
Date: Sun, 19 Jul 2020 08:03:41 -0700	[thread overview]
Message-ID: <20200719150341.GA11122@adacore.com> (raw)
In-Reply-To: <83zh7wgrwn.fsf@gnu.org>

> > Date: Sat, 18 Jul 2020 12:45:22 -0700
> > From: Joel Brobecker <brobecker@adacore.com>
> > Cc: kevinb@redhat.com, sandra@codesourcery.com, tom@tromey.com,
> > 	ssbssa@yahoo.de, ro@cebitec.uni-bielefeld.de, ludo@gnu.org,
> > 	eliz@gnu.org, cbiesinger@google.com
> > 
> >   * [EliZ]
> >     gdbserver: incorrect socklen_t configure test on mingw.org's MinGW
> >     https://sourceware.org/pipermail/gdb-patches/2020-July/170019.html
> > 
> >     Eli and Joel exchanged patches, but I don't see anything having
> >     been officially submitted yet?
> 
> Joel, are you waiting for me here?  If so, what shall I do?  I thought
> you'll go ahead and install the changes you sent me and I tested.

It must have been a misunderstanding. I was indeed hoping you would be
the one submitting the patch. I was only helping you re-generate the
configury scripts to help you avoid having to get the exact versions
we expect to use, when generating them. I would be happy to help submit
them for you if I wasn't already unsuccesful myself in submitting my
own patches :-(.

-- 
Joel


  reply	other threads:[~2020-07-19 15:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-18 19:45 Joel Brobecker
2020-07-19  2:28 ` Eli Zaretskii
2020-07-19 15:03   ` Joel Brobecker [this message]
2020-07-25  7:56     ` Eli Zaretskii
2020-07-20 11:34 ` Rainer Orth
2020-07-20 15:22   ` Joel Brobecker
2020-07-21 20:38 ` Tom Tromey
2020-07-22 12:57   ` Joel Brobecker
2020-07-22 20:32 ` Kevin Buettner
2020-07-23 18:43   ` 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=20200719150341.GA11122@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@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