From: Daniel Jacobowitz <drow@false.org>
To: Gaius Mulley <gaius@glam.ac.uk>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sources.redhat.com
Subject: Re: Entry for Modula-2 changes in NEWS?
Date: Fri, 19 May 2006 02:59:00 -0000 [thread overview]
Message-ID: <20060519025111.GA24267@nevyn.them.org> (raw)
In-Reply-To: <87zmhe3gk7.fsf@glam.ac.uk>
On Fri, May 19, 2006 at 03:16:08AM +0100, Gaius Mulley wrote:
> Joel Brobecker <brobecker@adacore.com> writes:
>
> > Hi Gaius,
> >
> > > feel free to use these words (or modify them in any way) if you
> > > decide that detail is warranted..
> >
> > I am happy to submit these changes for approval, but I think it would
> > make more sense if you did it. What do you think? Once approved, I can
> > port the change to the branch as well, if you prefer. It's not
> > difficult, but you need to check out the branch, which takes a bit of
> > time. I already have done it on my side.
>
> all done now,
I see you've modified NEWS on the branch. Please, three notes:
- Patches need to be sent to gdb-patches@.
- Changes shouldn't go onto a branch that haven't already gone onto
HEAD.
- And it's usually polite to post patches before checking them in;
for instance, Eli usually reviews documentation patches quickly
(and NEWS is part of the documentation now).
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-19 2:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 22:37 Joel Brobecker
2006-05-16 22:39 ` Gaius Mulley
[not found] ` <20060517154255.GF12531@adacore.com>
2006-05-18 1:21 ` Nick Roberts
2006-05-19 2:51 ` Gaius Mulley
2006-05-18 3:36 ` Daniel Jacobowitz
2006-05-18 14:36 ` Gaius Mulley
2006-05-19 2:54 ` Gaius Mulley
2006-05-19 2:59 ` Daniel Jacobowitz [this message]
2006-05-19 10:16 ` Gaius Mulley
2006-05-19 5:48 ` [patch] update for Modula-2 changes in NEWS Gaius Mulley
2006-05-19 10:25 ` Joel Brobecker
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=20060519025111.GA24267@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gaius@glam.ac.uk \
--cc=gdb@sources.redhat.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