From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Tom Tromey <tom@tromey.com>
Cc: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [RFC] [gdb] Move ChangeLog files to archive dir
Date: Tue, 28 Jul 2026 12:30:39 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2607210408540.64835@angie.orcam.me.uk> (raw)
In-Reply-To: <87pl0hwpay.fsf@tromey.com>
On Mon, 20 Jul 2026, Tom Tromey wrote:
> > 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.
>
> Is there anybody out there who wants to include these files in greps?
I don't think I've had a use specifically for greps, however I do look up
these old ChangeLog files occasionally, most recently just a few days ago
on the binutils side, when chasing very old changes, usually while trying
to figure out the context in the course of fixing bugs.
> If not we ought to git rm them. Personally I only ever end up viewing a
> ChangeLog by mistake, they aren't really useful IMNSHO.
If we were to drop them, we may have to consult FSF first though.
Maciej
prev parent reply other threads:[~2026-07-28 11:31 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
2026-07-20 17:20 ` Tom Tromey
2026-07-28 11:30 ` Maciej W. Rozycki [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=alpine.DEB.2.21.2607210408540.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