From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] [gdb] Move ChangeLog files to archive dir
Date: Fri, 26 Jun 2026 17:37:48 +0200 [thread overview]
Message-ID: <f5709f25-72b7-461b-9418-c085725469b9@suse.de> (raw)
In-Reply-To: <87echtwcb3.fsf@tromey.com>
On 6/26/26 5:28 PM, Tom Tromey wrote:
>>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
>
> Tom> We stopped updating ChangeLog files in 2021, and they are no longer
> Tom> maintained.
>
> Tom> If I want to see history, I use git log, so I don't use them for any purpose.
>
> Tom> And they're in my way when I'm searching for files, grepping, or refactoring
> Tom> using sed.
>
> Tom> Move them out of the way, into a root-level directory named archive
> Tom> (alternative names: legacy, deprecated, attic, stale, historical,
> Tom> unmaintained).
>
> Won't they still show up in greps?
>
The greps I do tend to be of the form:
...
$ find gdb* -type f | xargs grep ...
...
so for those, they won't show up.
> What if we just 'git rm' them instead?
> Or is this too extreme?
Assuming all the same information is present in the git logs, I'm fine
with that.
Thanks,
- Tom
next prev parent reply other threads:[~2026-06-26 15:38 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 [this message]
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
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=f5709f25-72b7-461b-9418-c085725469b9@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--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