From: Eli Zaretskii <eliz@gnu.org>
To: Siva Chandra <sivachandra@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [pushed/obv] DOC: Add space before the opening parenthesis in function descriptions
Date: Mon, 09 Jun 2014 14:48:00 -0000 [thread overview]
Message-ID: <8338fe2l6w.fsf@gnu.org> (raw)
In-Reply-To: <CAGyQ6gzcNyfSftYdPL6065WChG5V7bFg=znYDH+0F4DhGrj79g@mail.gmail.com>
> Date: Mon, 9 Jun 2014 07:23:27 -0700
> From: Siva Chandra <sivachandra@google.com>
>
> doc/
> 2014-06-09 Siva Chandra Reddy <sivachandra@google.com>
>
> * python.texi (Xmethod API): Add space before the opening
> parenthesis in function descriptions.
Thanks. As luck would have it, I also bumped into this today.
next prev parent reply other threads:[~2014-06-09 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 14:23 Siva Chandra
2014-06-09 14:48 ` Eli Zaretskii [this message]
2014-06-09 15:15 ` Joel Brobecker
2014-06-09 16:16 ` Eli Zaretskii
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=8338fe2l6w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sivachandra@google.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