public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Alan Hayward <Alan.Hayward@arm.com>,
	 Philippe Waroquiers <philippe.waroquiers@skynet.be>,
	 Andrew Burgess <andrew.burgess@embecosm.com>,
	 gdb-patches@sourceware.org
Subject: Re: GDB 8.2 branch 2018-06-11 Update
Date: Tue, 12 Jun 2018 00:19:00 -0000	[thread overview]
Message-ID: <87bmcg5017.fsf@redhat.com> (raw)
In-Reply-To: <20180611225629.GA31935@adacore.com> (Joel Brobecker's message of	"Mon, 11 Jun 2018 15:56:29 -0700")

On Monday, June 11 2018, Joel Brobecker wrote:

> Hello everyone,

Hi Joel,

>   * (SergioDJ) Implement IPv6 support for GDB/gdbserver
>     Latest update: received comments, waiting for new version:
>     https://www.sourceware.org/ml/gdb-patches/2018-06/msg00238.html
[...]
> I would like very much to cut the branch by end of this month at
> the very latest. After that, we get into the summer holidays where
> things start getting slow, so I'd rather start before then.
>
> Do you guys think you'll be able to make it?

Yeah, I am planning to submit a v2 before Friday, and hopefully get the
patch accepted before next week.  I'll keep you posted if anything
happens.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

  reply	other threads:[~2018-06-12  0:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-11 22:56 Joel Brobecker
2018-06-12  0:19 ` Sergio Durigan Junior [this message]
2018-06-12  8:29 ` Alan Hayward
2018-06-12 12:59   ` Simon Marchi
2018-06-12 21:57 ` Philippe Waroquiers
2018-06-19  6:07 ` Tom Tromey
2018-06-22 14:21   ` Joel Brobecker
2018-06-22 20:37     ` Tom Tromey

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=87bmcg5017.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=Alan.Hayward@arm.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    /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).