Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Gaius Mulley <gaius@glam.ac.uk>
To: Jim Blandy <jimb@codesourcery.com>
Cc: "Eli Zaretskii" <eliz@gnu.org>,  gdb-patches@sources.redhat.com
Subject: Re: Enhanced language support for Modula-2
Date: Thu, 11 May 2006 12:37:00 -0000	[thread overview]
Message-ID: <87mzdosqi4.fsf@glam.ac.uk> (raw)
In-Reply-To: <vt2bqu5y2ox.fsf@theseus.home.>

Jim Blandy <jimb@codesourcery.com> writes:

> > also enclosed is a proposed set of ChangeLog entries:
> 
> Looks great!

thanks..

> Two points to fix when you commit; don't bother re-posting the patch
> for review:
> 
> - There's still an overly long line in m2-valprint.c, in the
>   TYPE_CODE_STRUCT case.

ok I'll fix it..

> - Similarly, there's a separate ChangeLog for the doc directory; the
>   entry for your change to gdb.texinfo should go in gdb/doc/ChangeLog,
>   not gdb/ChangeLog.  And generally, we put section names in parens
>   after the filename, as we do for functions in C files.  Like so:
> 
>       * gdb.texinfo (M2 Types): New section.

ok.

> I see that you have a copyright assignment on file.  Do you have
> commit access to GDB?  If not, we'll have to get you set up with that
> first.

no I don't have commit access. Commit access would be great, thanks.

> If you do, then make a commit to gdb/MAINTAINERS, adding yourself to
> "Write After Approval", with an appropriate ChangeLog entry.  Then go
> ahead and commit the rest of the patch.

sure, will do.

regards,
Gaius


  reply	other threads:[~2006-05-11 12:37 UTC|newest]

Thread overview: 45+ 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 [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
2006-02-15 23:15 Gaius Mulley
2006-02-16  0:20 ` Jim Blandy
2006-02-16 11:06   ` Gaius Mulley
2006-02-20 15:05   ` Daniel Jacobowitz
2006-02-20 21:42     ` Jim Blandy
2006-02-21 11:06       ` Gaius Mulley
2006-02-21 19:01         ` Jim Blandy
2006-02-25 13:17           ` Gaius Mulley
2006-02-26  5:44             ` Jim Blandy
2006-02-26  5:46               ` Daniel Jacobowitz
2006-02-28  5:37               ` Gaius Mulley
2006-02-28 13:53                 ` Jim Blandy
2006-03-02  8:57                   ` Gaius Mulley
2006-03-02 17:27                     ` Jim Blandy
2006-02-21 19:21         ` Jim Blandy
2006-02-21 20:51           ` Eli Zaretskii
2006-02-21 20:50         ` Eli Zaretskii
2006-02-21 20:57           ` Mark Kettenis
2006-02-22  5:33             ` Eli Zaretskii
2006-02-22 18:36               ` Eli Zaretskii
2006-02-16  4:34 ` Eli Zaretskii
2006-02-16 11:11   ` Gaius Mulley

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=87mzdosqi4.fsf@glam.ac.uk \
    --to=gaius@glam.ac.uk \
    --cc=eliz@gnu.org \
    --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