From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Re: [autodeps] gnu-nat, autogenerated files
Date: Fri, 12 Sep 2008 10:44:00 -0000 [thread overview]
Message-ID: <200809121144.05946.pedro@codesourcery.com> (raw)
In-Reply-To: <uljxxpw63.fsf@gnu.org>
On Friday 12 September 2008 06:05:01, Joel Brobecker wrote:
> > +
> > +NAT_GENERATED_FILES = notify_S.h notify_S.c process_reply_S.h
> > process_reply_S.c \
>
> Just a very minor comment: I wonder if you might have exceeded 80 chars
> on this line.
Sorry about that. Fixed.
On Friday 12 September 2008 10:09:56, Eli Zaretskii wrote:
> Pedro's patch for the documentation looks fine to me.
Thanks guys. I've checked it in.
--
Pedro Alves
prev parent reply other threads:[~2008-09-12 10:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 15:07 Pedro Alves
2008-09-09 16:09 ` Tom Tromey
2008-09-09 16:18 ` Daniel Jacobowitz
2008-09-09 16:28 ` Tom Tromey
2008-09-10 18:01 ` Joel Brobecker
2008-09-10 18:13 ` Daniel Jacobowitz
2008-09-10 18:49 ` Pedro Alves
2008-09-12 5:06 ` Joel Brobecker
2008-09-12 9:10 ` Eli Zaretskii
2008-09-12 10:44 ` Pedro Alves [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=200809121144.05946.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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