From: Olivier Certner <ocert.dev@free.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63072@debbugs.gnu.org
Subject: bug#63072: 28.2; CC Mode: Fix "bsd" style and add "freebsd" and "openbsd" ones
Date: Wed, 26 Apr 2023 15:09:21 +0200 [thread overview]
Message-ID: <5569144.NofZdxuNk6@ravel> (raw)
In-Reply-To: <83ttx3szmr.fsf@gnu.org>
> If the styles don't change in practice, then I'm okay with adding
> them. But then I wonder why you bothered to mention the fact that
> they do change.
I thought this was clear, but apparently not. I mentioned the possibility of a
change, yes, because you and I care about backwards compatibility. To quote
you: "I don't think we can change a style that was in use for such a long
time".
There may be changes in the project styles, maybe next month, maybe in ten
years, maybe in twenty. I do not think the probability is 0 over such a long
period of time. What I would not want is you or someone else telling me in 10
or 20 years, after such a change: "I don't think we can change a style that
was in use for such a long time". What I want instead is that, e.g., "freebsd"
can be changed as necessary. I specifically do not want to then be told to
create another style named "freebsd2" or whatever. For that to be possible,
users must be warned that these styles, although almost always stable, are
not, and will not, be set in stone for eternity, contrary to, perhaps, "bsd"
or "whitesmith". And I even offered a scheme with additional styles that will
never change, if you think that is useful (I think it might be and is so cheap
to implement that I think we should do it anyway, even if in the end nobody
uses it).
Is that clear now?
--
Olivier Certner
next prev parent reply other threads:[~2023-04-26 13:09 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 [this message]
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
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=5569144.NofZdxuNk6@ravel \
--to=ocert.dev@free.fr \
--cc=63072@debbugs.gnu.org \
--cc=eliz@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.
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).