Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@mips.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: drow@false.org, gdb-patches@sourceware.org, chris@mips.com,
	     macro@linux-mips.org
Subject: Re: ser-unix.c: Add hardware flow control support
Date: Tue, 22 May 2007 10:57:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.61.0705221112320.27238@perivale.mips.com> (raw)
In-Reply-To: <uk5v2kkkd.fsf@gnu.org>

On Mon, 21 May 2007, Eli Zaretskii wrote:

> This part is fine, but please add a @kindex index entry for the new
> command, as we do in general for every other.

 OK, and this one happens to hit this rule?  Applied now with your 
suggested changes.

  Maciej


  reply	other threads:[~2007-05-22 10:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30 11:55 Maciej W. Rozycki
2007-03-30 12:08 ` Daniel Jacobowitz
2007-05-02 14:11   ` Maciej W. Rozycki
2007-05-21 12:22     ` Maciej W. Rozycki
2007-05-21 12:50       ` Daniel Jacobowitz
2007-05-21 20:08       ` Eli Zaretskii
2007-05-22 10:57         ` Maciej W. Rozycki [this message]
2007-03-30 12:26 ` 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=Pine.LNX.4.61.0705221112320.27238@perivale.mips.com \
    --to=macro@mips.com \
    --cc=chris@mips.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=macro@linux-mips.org \
    /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