From: Joel Brobecker <brobecker@adacore.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Simon Marchi <simark@simark.ca>,
gdb-patches@sourceware.org,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFA] Rename gdb/ChangeLog to gdb/ChangeLog-2021
Date: Thu, 8 Jul 2021 05:56:41 -0700 [thread overview]
Message-ID: <20210708125641.GA229653@adacore.com> (raw)
In-Reply-To: <e57038ca-f02f-5b91-9f8a-0711f5b55682@suse.de>
> $ find gdb* -name ChangeLog
> gdb/doc/ChangeLog
> gdb/testsuite/ChangeLog
> gdb/stubs/ChangeLog
> gdbserver/ChangeLog
> gdbsupport/ChangeLog
> ...
>
> Maybe a good idea to rename those as well? Or am I missing something?
Either that, or perhaps write a blurb at the start of the ChangeLog
file explaining that they are no longer used. These ChangeLog files
weren't rotated each year, so it might not make as much sense to
renaming them with a year extension (but I wouldn't object -- although
a range of years might make better sense in that case).
We have to include also the ChangeLog in the sim, and there's
perhaps also include/gdb.
--
Joel
next prev parent reply other threads:[~2021-07-08 12:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 17:54 FYI/HEAD: Patches applied to branch master Joel Brobecker
2021-07-03 17:54 ` [release/HEAD 1/2] Bump version to 12.0.50.DATE-git Joel Brobecker
2021-07-03 17:54 ` [release/HEAD 2/2] Update NEWS post GDB 11 branch creation Joel Brobecker
2021-07-03 22:09 ` Simon Marchi
2021-07-03 23:27 ` Joel Brobecker
2021-07-03 23:32 ` [RFA] Rename gdb/ChangeLog to gdb/ChangeLog-2021 Joel Brobecker
2021-07-04 4:28 ` Eli Zaretskii via Gdb-patches
2021-07-04 22:47 ` Simon Marchi via Gdb-patches
2021-07-06 16:16 ` Joel Brobecker
2021-07-08 7:45 ` Tom de Vries
2021-07-08 12:56 ` Joel Brobecker [this message]
2021-08-18 0:29 ` Mike Frysinger via Gdb-patches
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=20210708125641.GA229653@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--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