From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63072@debbugs.gnu.org, Olivier Certner <ocert.dev@free.fr>
Subject: bug#63072: 28.2; CC Mode: Fix "bsd" style and add "freebsd" and "openbsd" ones
Date: Tue, 5 Sep 2023 09:01:43 -0700 [thread overview]
Message-ID: <CADwFkmmAb5LFVJL1mp0fv_6OmRNqHXH85HCkbLDsO6UZq8Ly8g@mail.gmail.com> (raw)
In-Reply-To: <83cz3qtyno.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 26 Apr 2023 19:07:39 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Olivier Certner <ocert.dev@free.fr>
>> Cc: 63072@debbugs.gnu.org
>> Date: Wed, 26 Apr 2023 15:53:21 +0200
>>
>> > Given all that, I'm not sure we should single out these new styles at
>> > all. Once in 10 years any constant is eligible for a change.
>>
>> Then maybe it's my turn not to understand. To me, allowing them to be changed
>> in 10 years from now is singling them out with respect to, e.g., "bsd" which,
>> as you said yourself in preamble, should not be changed after all these years.
>>
>> Apart from this caveat, I'm fine with your conclusion.
>
> Let's see that patch of yours, then.
Oliver, did you have a chance to look into this?
Thanks.
next prev parent reply other threads:[~2023-09-05 16:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 17:49 bug#63072: 28.2; CC Mode: Fix "bsd" style and add "freebsd" and "openbsd" ones Olivier Certner
2023-04-25 18:03 ` Eli Zaretskii
2023-04-25 20:57 ` Olivier Certner
2023-04-26 5:50 ` Eli Zaretskii
2023-04-26 7:28 ` Olivier Certner
2023-04-26 9:13 ` Eli Zaretskii
2023-04-26 9:31 ` Olivier Certner
2023-04-26 10:31 ` Eli Zaretskii
2023-04-26 13:09 ` Olivier Certner
2023-04-26 13:32 ` Eli Zaretskii
2023-04-26 13:53 ` Olivier Certner
2023-04-26 16:07 ` Eli Zaretskii
2023-09-05 16:01 ` Stefan Kangas [this message]
2023-09-15 12:41 ` Stefan Kangas
2023-09-19 16:15 ` Olivier Certner
2023-09-21 15:22 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmmAb5LFVJL1mp0fv_6OmRNqHXH85HCkbLDsO6UZq8Ly8g@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=63072@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ocert.dev@free.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).