From: Eli Zaretskii <eliz@gnu.org>
To: Orgad Shaneh <orgads@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Support MSYS2 platform
Date: Sun, 03 Mar 2024 12:54:34 +0200 [thread overview]
Message-ID: <86il23oaad.fsf@gnu.org> (raw)
In-Reply-To: <20240303094330.1237-1-orgad.shaneh@audiocodes.com> (message from Orgad Shaneh on Sun, 3 Mar 2024 11:43:22 +0200)
> From: Orgad Shaneh <orgads@gmail.com>
> Cc: Orgad Shaneh <orgads@gmail.com>
> Date: Sun, 3 Mar 2024 11:43:22 +0200
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 2638b3e0d9c..f1a50867375 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -13,6 +13,8 @@
> the background, resulting in faster startup. This can be controlled
> using "maint set dwarf synchronous".
>
> +* Added built-in support for building on MSYS2 platform.
> +
This is not how the GDB project announces new targets in gdb/NEWS. We
do it like this:
* New targets
GNU/Linux/LoongArch (gdbserver) loongarch*-*-linux*
GNU/Linux/CSKY (gdbserver) csky*-*linux*
AMDGPU amdgcn-*-*
So you need to start a "New targets" section in the "since GDB 14"
part, and then add this new target there using the above style.
Thanks.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2024-03-03 10:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 7:58 [PATCH] Support MSYS platform Orgad Shaneh
2024-03-03 8:56 ` Eli Zaretskii
2024-03-03 9:46 ` Orgad Shaneh
2024-03-03 10:57 ` Eli Zaretskii
2024-03-03 11:04 ` Orgad Shaneh
2024-03-03 9:43 ` [PATCH] Support MSYS2 platform Orgad Shaneh
2024-03-03 10:54 ` Eli Zaretskii [this message]
2024-03-03 11:06 ` Orgad Shaneh
2024-03-03 11:07 ` Orgad Shaneh
2024-03-08 17:36 ` Tom Tromey
2024-03-08 19:41 ` Eli Zaretskii
2024-03-09 20:47 ` Orgad Shaneh
2024-03-10 14:27 ` Tom Tromey
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=86il23oaad.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=orgads@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).