From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] [gdb] Move ChangeLog files to archive dir
Date: Sun, 19 Jul 2026 20:23:57 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2607192017470.64835@angie.orcam.me.uk> (raw)
In-Reply-To: <9e63cbaf-a052-43cf-88f7-619aae089d67@suse.de>
On Mon, 13 Jul 2026, Tom de Vries wrote:
> I've decided to commit this patch. My guess is that complete removal is more
> likely to run into objections from other maintainers.
FWIW I have done:
$ find ... -not -name 'ChangeLog*' ...
since forever, even when ChangeLog files were still actively updated (they
still are for other toolchain components) and it works for me either way,
never had to bother about them. Similarly for .git and other such stuff.
Maciej
next prev parent reply other threads:[~2026-07-19 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-20 11:40 Tom de Vries
2026-06-23 15:59 ` Keith Seitz
2026-06-26 15:28 ` Tom Tromey
2026-06-26 15:37 ` Tom de Vries
2026-07-13 11:30 ` Tom de Vries
2026-07-19 19:23 ` Maciej W. Rozycki [this message]
2026-07-20 17:20 ` Tom Tromey
2026-07-28 11:30 ` Maciej W. Rozycki
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=alpine.DEB.2.21.2607192017470.64835@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
--cc=tom@tromey.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