Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Remove support for the Common Trace Format (CTF)
Date: Sun, 10 May 2026 23:56:57 -0400	[thread overview]
Message-ID: <87y0hqy4xi.fsf@sergiodj.net> (raw)
In-Reply-To: <30dde5a1-3402-479a-824b-10768006ea7d@polymtl.ca> (Simon Marchi's message of "Sun, 10 May 2026 21:25:25 -0400")

On Sunday, 10 May 2026, Simon Marchi wrote:

> On 2026-05-10 12:42, Sergio Durigan Junior wrote:
>>> The patch doesn't contain the generated files (configure & al), please
>>> submit a patch with the generated files.
>> 
>> Hm, I was following the instructions from
>> <https://sourceware.org/gdb/wiki/DeveloperTips#Editing_configure.ac>.
>> Are they out-of-date?  I'm happy to update the wiki if that's the case.
>
> Weird, in all my time contributing to GDB we always sent the generated
> files, unless the resulting patch was too big to send on the list.

Yeah, that's what I remember from the old times as well.  I took the
liberty to edit the wiki page and invert that sentence.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

      parent reply	other threads:[~2026-05-11  3:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-10  2:28 Sergio Durigan Junior
2026-05-10  4:47 ` Eli Zaretskii
2026-05-10 12:43 ` Simon Marchi
2026-05-10 16:42   ` Sergio Durigan Junior
2026-05-11  1:25     ` Simon Marchi
2026-05-11  3:52       ` Sergio Durigan Junior
2026-05-11  3:56       ` Sergio Durigan Junior [this message]

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=87y0hqy4xi.fsf@sergiodj.net \
    --to=sergiodj@sergiodj.net \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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