From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [RFA/Doco] Document new <data-dir>/system-gdbinit area
Date: Tue, 21 May 2013 17:37:00 -0000 [thread overview]
Message-ID: <837gisute4.fsf@gnu.org> (raw)
In-Reply-To: <519B9404.2020407@redhat.com>
> Date: Tue, 21 May 2013 16:34:28 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: gdb-patches@sourceware.org
>
> On 05/21/2013 10:24 AM, Joel Brobecker wrote:
>
> > Should I also add a NEWS entry for this?
>
> IMO, yes.
I agree. This kind of changes will go unnoticed unless we announce
them where most people will look.
next prev parent reply other threads:[~2013-05-21 17:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 9:25 Joel Brobecker
2013-05-21 15:34 ` Pedro Alves
2013-05-21 17:37 ` Eli Zaretskii [this message]
2013-05-21 17:17 ` Eli Zaretskii
2013-05-22 6:28 ` Joel Brobecker
2013-05-22 14:54 ` Eli Zaretskii
2013-05-23 6:08 ` Checked in: " Joel Brobecker
2013-05-24 1:33 ` asmwarrior
2013-05-24 4:53 ` Joel Brobecker
2013-05-24 5:06 ` Joel Brobecker
2013-05-24 6:24 ` Eli Zaretskii
2013-05-22 6:44 ` 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=837gisute4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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