Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Julio Guerra <julio@farjump.io>
Cc: Tom Tromey <tom@tromey.com>,
	 "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>,
	 Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH] Install fileio.h to share File I/O protocol type definitions
Date: Fri, 07 Sep 2018 22:08:00 -0000	[thread overview]
Message-ID: <87r2i5ufjk.fsf@tromey.com> (raw)
In-Reply-To: <01020164d3075dd7-c5101668-597f-4dd0-81ef-d7a1bc2642fc-000000@eu-west-1.amazonses.com>	(Julio Guerra's message of "Wed, 25 Jul 2018 20:00:32 +0000")

>>>>> "Julio" == Julio Guerra <julio@farjump.io> writes:

Thanks for your patience on this repsonse.

The gdb rule is that you can ping a patch (or in this case, IMO, really
any question) after 2 weeks, and then weekly thereafter.  This may be
uncomfortable (I never really got into it) but it really is ok.

>> It seems like it would be a good idea to have some documentation for
>> this, if it's something we intend to support.

Julio> The documentation already talks about these types here
Julio> https://sourceware.org/gdb/onlinedocs/gdb/Protocol_002dspecific-Representation-of-Datatypes.html#Protocol_002dspecific-Representation-of-Datatypes
Julio> But do you want me to add some documentation about this file being
Julio> installed before the list?

I think that would be a good idea.

thanks,
Tom


      reply	other threads:[~2018-09-07 22:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180709093410.63068-1-julio@farjump.io>
2018-07-09  9:34 ` Julio Guerra
2018-07-25 19:37   ` Tom Tromey
     [not found]     ` <9f54db97-2e20-1935-c730-e6036a5809e0@farjump.io>
2018-07-25 20:01       ` Julio Guerra
2018-09-07 22:08         ` Tom Tromey [this message]

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=87r2i5ufjk.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=julio@farjump.io \
    --cc=palves@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