Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] [gdb] Remove unnecessary defs.h/common-defs.h includes
Date: Tue, 21 Apr 2026 15:53:09 -0400	[thread overview]
Message-ID: <d8ec106f-548e-49c8-8401-d176ca840828@simark.ca> (raw)
In-Reply-To: <20260421194011.1982212-1-tdevries@suse.de>

On 4/21/26 3:40 PM, Tom de Vries wrote:
> I asked an AI to review a patch that added a new file, and it mentioned I
> should add an include of defs.h as first include.
> 
> That used to be true, but since commit 18d2988e5da ("gdb, gdbserver,
> gdbsupport: remove includes of early headers") that's not the case anymore.

Btw, this is the kind of details that we could put in an AGENTS.md file
(or similar), if it doesn't offend too many people.  AIs are much more
efficient if they know the conventions of the project ahead of time.

Approved-By: Simon Marchi <simon.marchi@efficios.com>

Simon


  reply	other threads:[~2026-04-21 19:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 19:40 Tom de Vries
2026-04-21 19:53 ` Simon Marchi [this message]
2026-04-21 21:28   ` Tom de Vries

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=d8ec106f-548e-49c8-8401-d176ca840828@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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