From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Siddhesh Poyarekar <sipoyare@redhat.com>,
Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 1/5] gdb: fix minor grammar error in SECURITY.txt
Date: Mon, 12 Oct 2026 14:49:10 +0100 [thread overview]
Message-ID: <9e46cacf1317da9c60f2979870e438f10d02bd82.1791812758.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1791812758.git.aburgess@redhat.com>
There's a missing 'to' in the SECURITY.txt document. Fixed in this
commit.
---
gdb/SECURITY.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/SECURITY.txt b/gdb/SECURITY.txt
index 008bf88d230..f4ddebe3f03 100644
--- a/gdb/SECURITY.txt
+++ b/gdb/SECURITY.txt
@@ -17,7 +17,7 @@ Introduction
Policy Objectives
-----------------
- The objective of this policy is define what the GDB project
+ The objective of this policy is to define what the GDB project
considers a security bug and what is a non-security bug, and how
bugs can be reported.
--
2.25.4
next prev parent reply other threads:[~2026-10-12 13:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 13:49 [PATCH 0/5] SECURITY.txt changes Andrew Burgess
2026-10-12 13:49 ` Andrew Burgess [this message]
2026-10-14 15:02 ` [PATCH 1/5] gdb: fix minor grammar error in SECURITY.txt Tom Tromey
2026-10-12 13:49 ` [PATCH 2/5] gdb: extend SECURITY.txt to highlight additional remote debugging risks Andrew Burgess
2026-10-13 15:22 ` Siddhesh Poyarekar
2026-10-14 15:08 ` Tom Tromey
2026-10-14 16:10 ` Siddhesh Poyarekar
2026-10-16 14:24 ` Andrew Burgess
2026-10-16 14:27 ` Siddhesh Poyarekar
2026-10-12 13:49 ` [PATCH 3/5] gdb: extend SECURITY.txt discussion of DWARF/BFD parser bugs Andrew Burgess
2026-10-13 15:30 ` Siddhesh Poyarekar
2026-10-14 15:12 ` Tom Tromey
2026-10-14 16:16 ` Siddhesh Poyarekar
2026-10-14 17:28 ` Carlos O'Donell
2026-10-12 13:49 ` [PATCH 4/5] gdb: in SECURITY.txt, add notes on reporting exec and debug bugs Andrew Burgess
2026-10-12 13:49 ` [PATCH 5/5] gdb: improve SECURITY.txt relating to embedded language bugs Andrew Burgess
2026-10-14 15:44 ` [PATCH 0/5] SECURITY.txt changes 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=9e46cacf1317da9c60f2979870e438f10d02bd82.1791812758.git.aburgess@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sipoyare@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