From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA/NEWS] Move misplaced entry...
Date: Thu, 15 Jan 2009 10:35:00 -0000 [thread overview]
Message-ID: <20090115103444.GT31296@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 281 bytes --]
Hello,
On my way to adding an entry for x86_64/MinGW support, I noticed that
one command was documented in the wrong section:
* NEWS: Move the documentation of "info os processes" to
the appropriate section (documenting the new commands).
OK to apply?
--
Joel
[-- Attachment #2: NEWS-move.diff --]
[-- Type: text/plain, Size: 480 bytes --]
diff --git a/gdb/NEWS b/gdb/NEWS
index 027ab02..d1e0a91 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -186,13 +186,13 @@ macro undef
These allow macros to be defined, undefined, and listed
interactively.
+info os processes
+ Show operating system information about processes.
+
* New native configurations
x86/x86_64 Darwin i[34567]86-*-darwin*
-info os processes
- Show operating system information about processes.
-
* New targets
x86 DICOS i[34567]86-*-dicos*
next reply other threads:[~2009-01-15 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 10:35 Joel Brobecker [this message]
2009-01-15 19:07 ` Eli Zaretskii
2009-01-16 4:32 ` 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=20090115103444.GT31296@adacore.com \
--to=brobecker@adacore.com \
--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