From: Daniel Jacobowitz <drow@false.org>
To: Gaius Mulley <gaius@glam.ac.uk>
Cc: gdb-patches@sources.redhat.com,
Joel Brobecker <brobecker@adacore.com>,
Eli Zaretskii <eliz@gnu.org>, Jim Blandy <jimb@codesourcery.com>
Subject: Re: [commit]: Re: Enhanced language support for Modula-2
Date: Sat, 13 May 2006 16:43:00 -0000 [thread overview]
Message-ID: <20060513162355.GA6564@nevyn.them.org> (raw)
In-Reply-To: <87zmhlgc0y.fsf_-_@glam.ac.uk>
On Sat, May 13, 2006 at 04:49:49PM +0100, Gaius Mulley wrote:
>
> Hi,
>
> a small note to say that I've applied the Modula-2 enhancement patches
> to the gdb cvs. Many thanks for all the guidance,
Hi Gaius,
Great to see this in. And I see you've been working on the ChangeLog
entry. But it still needs a bit of work, so here's some pointers (some
of these are from the GNU Coding Standards,
http://www.gnu.org/prep/standards/, others are only implicit there but
GDB tries to follow them carefully).
> 2006-05-09 Gaius Mulley <gaius@glam.ac.uk>
Two spaces between name and email address in the header, please.
> * gdb/m2-lang.h: added function extern prototypes for
> m2_is_long_set and get_long_set_bounds.
Path names should be relative to the directory containing the
ChangeLog, so just "m2-lang.h". Entries should start with a capital
letter and end with a period (although sentence fragments are fine).
> * gm2/m2-typeprint.c: This file has been completely
> replaced to reflect the Modula-2 syntax rather than call the
> c_print_type function.
We don't usually use explanatory sentences, just the actual changes; a
bit strange, yes...
> * gdb/dwarf2read.c: added ability to detect the language
> Modula-2 and handle SET and CHAR types.
The current version says:
* gdb/dwarf2read.c: added ability to detect the language
Modula-2
and handle SET and CHAR types.
Again about the pathname and the explanatory sentences, but also the
wrapping; what's the stray newline for?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-13 16:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 13:23 Gaius Mulley
2006-04-20 14:35 ` Eli Zaretskii
2006-04-20 18:47 ` Mark Kettenis
2006-04-20 18:54 ` Eli Zaretskii
2006-05-04 7:17 ` Gaius Mulley
2006-05-04 15:37 ` Daniel Jacobowitz
2006-05-04 18:01 ` Jim Blandy
2006-05-08 14:09 ` Gaius Mulley
2006-05-08 17:47 ` Jim Blandy
2006-05-09 22:57 ` Gaius Mulley
2006-05-10 21:45 ` Jim Blandy
2006-05-11 12:37 ` Gaius Mulley
2006-05-12 18:18 ` Joel Brobecker
2006-05-12 18:27 ` Jim Blandy
2006-05-13 13:31 ` Gaius Mulley
2006-05-13 16:24 ` [commit]: " Gaius Mulley
2006-05-13 16:43 ` Daniel Jacobowitz [this message]
2006-05-13 18:56 ` Gaius Mulley
2006-05-13 19:08 ` Daniel Jacobowitz
2006-05-13 19:44 ` Gaius Mulley
2006-05-13 11:02 ` Gaius Mulley
2006-05-08 21:03 ` Eli Zaretskii
2006-05-04 16:12 ` 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=20060513162355.GA6564@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gaius@glam.ac.uk \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@codesourcery.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