From: Eli Zaretskii <eliz@gnu.org>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: dje@google.com, gdb-patches@sourceware.org
Subject: Re: [PATCH/RFA] Introduce new $_isvoid() convenience function
Date: Sat, 14 Sep 2013 07:00:00 -0000 [thread overview]
Message-ID: <83d2obhoqy.fsf@gnu.org> (raw)
In-Reply-To: <m37gekxvzk.fsf@redhat.com>
> From: Sergio Durigan Junior <sergiodj@redhat.com>
> Cc: dje@google.com, gdb-patches@sourceware.org
> Date: Fri, 13 Sep 2013 18:17:03 -0300
>
> On Friday, September 13 2013, Eli Zaretskii wrote:
>
> >> From: Sergio Durigan Junior <sergiodj@redhat.com>
> >> Cc: dje@google.com, gdb-patches@sourceware.org
> >> Date: Fri, 13 Sep 2013 16:40:52 -0300
> >>
> >> > This is fine, but I would also include an example with $_exitcode.
> >>
> >> I intend to expand this explanation when I resubmit the patch for
> >> $_exitsignal. In fact, I will add another example showing the behavior
> >> of $_exitsignal and $_exitcode. But if you wish, I can add $_exitcode
> >> here as well.
> >
> > It would be best to have the explanation in both places, or at least a
> > cross-reference from one to the other.
>
> WDYT of this version?
This is great, thanks.
next prev parent reply other threads:[~2013-09-14 7:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 20:11 Sergio Durigan Junior
2013-09-12 23:59 ` Doug Evans
2013-09-13 6:42 ` Sergio Durigan Junior
2013-09-13 7:30 ` Eli Zaretskii
2013-09-13 17:45 ` Sergio Durigan Junior
2013-09-13 19:33 ` Eli Zaretskii
2013-09-13 19:41 ` Sergio Durigan Junior
2013-09-13 19:47 ` Eli Zaretskii
2013-09-13 21:17 ` Sergio Durigan Junior
2013-09-14 7:00 ` Eli Zaretskii [this message]
2013-09-16 17:19 ` Sergio Durigan Junior
2013-09-16 17:23 ` Doug Evans
2013-09-16 17:47 ` 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=83d2obhoqy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--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