From: Paul Smith via Gdb <gdb@sourceware.org>
To: Guinevere Larsen <guinevere@redhat.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Improve GDB's first user experience by reducing "print_gdb_version" output
Date: Tue, 27 May 2025 17:38:57 -0400 [thread overview]
Message-ID: <ecc728082ea5416ec35c2e4d2720a353c2f4508e.camel@gnu.org> (raw)
In-Reply-To: <0bfd51f7-2246-475c-b171-8dde8474227a@redhat.com>
On Tue, 2025-05-27 at 17:43 -0300, Guinevere Larsen via Gdb wrote:
> I'm sending this here in case there is some rule that forces us to
> write the copyright or free software status at initialization, before
> spending the time to turn this into a patch.
I had remembered that interactive programs should generate copyright
information at startup, but the most I can find in the current GNU
Maintainer's manual is:
> Sometimes a program has an overall copyright notice that refers to
> the whole program. It might be in the README file, or it might be
> displayed when the program starts up. This copyright notice should
> mention the year of completion of the most recent major version; it
> can mention years of completion of previous major versions, but that
> is optional.
https://www.gnu.org/prep/maintain/maintain.html#Copyright-Notices
Which is a "might" not a "should" or "must".
next prev parent reply other threads:[~2025-05-27 21:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 20:43 Guinevere Larsen via Gdb
2025-05-27 21:38 ` Paul Smith via Gdb [this message]
2025-05-28 7:33 ` Phi Debian via Gdb
2025-05-28 12:19 ` Eli Zaretskii via Gdb
2025-05-28 12:24 ` Guinevere Larsen via Gdb
2025-05-28 13:04 ` Paul Smith via Gdb
[not found] ` <CAJOr74gc9zeHQGST3eufT9zYJEsdEkO4m4xgxhQyQNE3kpSUNw@mail.gmail.com>
2025-05-29 9:16 ` Eli Zaretskii via Gdb
2025-05-28 7:44 ` Mark Wielaard
2025-05-28 12:30 ` Guinevere Larsen via Gdb
2025-05-30 11:22 ` Florian Weimer via Gdb
2025-05-30 20:39 ` Mark Wielaard
2025-05-28 11:47 ` Eli Zaretskii via Gdb
2025-05-28 11:39 ` Eli Zaretskii via Gdb
2025-05-28 12:15 ` Guinevere Larsen via Gdb
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=ecc728082ea5416ec35c2e4d2720a353c2f4508e.camel@gnu.org \
--to=gdb@sourceware.org \
--cc=guinevere@redhat.com \
--cc=psmith@gnu.org \
/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