public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org, palves@redhat.com,
	jan.kratochvil@redhat.com, fercerpav@gmail.com,
	sekiriki@gmail.com, armandsmailings@home.nl
Subject: Re: [PATCH v2] Implement IPv6 support for GDB/gdbserver
Date: Fri, 15 Jun 2018 07:12:00 -0000	[thread overview]
Message-ID: <831sd834nj.fsf@gnu.org> (raw)
In-Reply-To: <20180615002427.24949-1-sergiodj@redhat.com> (message from Sergio	Durigan Junior on Thu, 14 Jun 2018 20:24:27 -0400)

> From: Sergio Durigan Junior <sergiodj@redhat.com>
> Cc: Pedro Alves <palves@redhat.com>,
> 	Eli Zaretskii <eliz@gnu.org>,
> 	Jan Kratochvil <jan.kratochvil@redhat.com>,
> 	Paul Fertser <fercerpav@gmail.com>,
> 	Tsutomu Seki <sekiriki@gmail.com>,
> 	Armand Scholtes <armandsmailings@home.nl>,
> 	Sergio Durigan Junior <sergiodj@redhat.com>
> Date: Thu, 14 Jun 2018 20:24:27 -0400
> 
> Changes from v1:
> 
> - s/hostnames/addresses/ on NEWS.
> 
> - Simplify functions on netstuff.c.  Add new defines for
>   GDB_NI_MAX_ADDR and GDB_NI_MAX_PORT.  Make
>   parse_hostname_without_prefix return a struct parsed_hostname.
> 
> - Use AF_UNSPEC instead of AF_INET by default on unprefixed
>   connections.
> 
> - Simplify and modernize things on gdbreplay.c.
> 
> - Implement new GDB_TEST_SOCKETHOST mechanism for testing things with
>   any type of hostname/address.
> 
> - Simplify things on boards/*.exp because of the above.
> 
> - Rewrite net_open to support multiple sockets/connections with
>   timeout/retry.
> 
> - Improve IPv6 example on documentation.

Thanks, the documentation parts are okay.

  reply	other threads:[~2018-06-15  7:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23 21:48 [PATCH] " Sergio Durigan Junior
2018-05-23 23:40 ` Eli Zaretskii
2018-05-24  0:41   ` Sergio Durigan Junior
2018-05-24 16:54     ` Eli Zaretskii
2018-05-25  1:57       ` Sergio Durigan Junior
2018-05-31 20:10 ` Sergio Durigan Junior
2018-06-06 12:26 ` Pedro Alves
2018-06-08  1:13   ` Sergio Durigan Junior
2018-06-08 13:53     ` Pedro Alves
2018-06-08 17:47       ` Sergio Durigan Junior
2018-06-08 18:44         ` Pedro Alves
2018-06-08 19:28           ` Pedro Alves
2018-06-08 19:51             ` Pedro Alves
2018-06-08 20:43               ` Sergio Durigan Junior
2018-06-08 21:21           ` Sergio Durigan Junior
2018-06-08 21:51             ` Pedro Alves
2018-06-08 22:01               ` Sergio Durigan Junior
2018-06-15  0:25 ` [PATCH v2] " Sergio Durigan Junior
2018-06-15  7:12   ` Eli Zaretskii [this message]
2018-06-20 15:24   ` Pedro Alves
2018-06-21  4:54     ` Sergio Durigan Junior
2018-07-07 20:47 ` [PATCH v3] " Sergio Durigan Junior
2018-07-11 12:55   ` Pedro Alves
2018-07-11 19:13     ` Sergio Durigan Junior
2018-07-11 19:16 ` [PATCH v4] " Sergio Durigan Junior
2018-07-11 21:48   ` Pedro Alves
2018-07-11 23:43     ` Sergio Durigan Junior

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=831sd834nj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=armandsmailings@home.nl \
    --cc=fercerpav@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=palves@redhat.com \
    --cc=sekiriki@gmail.com \
    --cc=sergiodj@redhat.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).