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 09:28:17 +0200 [thread overview]
Message-ID: <2624808.XrqEPMHAR6@ravel> (raw)
In-Reply-To: <83cz3rur7v.fsf@gnu.org>
Hi,
> If documented that these styles change to follow the corresponding
> projects, it might be okay, but do we really want to commit ourselves
> to follow them from now to eternity? That's a non-trivial maintenance
> burden, unless the projects themselves take that up upon themselves,
> and will be submitting changes whenever their conventions change.
But I never said we would commit to that. On the contrary, what I would like
is that the documentation says clearly that "freebsd" and "openbsd" may
change, so that people are aware they cannot rely on these styles to always
remain the same (contrary to the old styles). So that's rather a non-
commitment.
Additionally, these changes will be exceedingly rare, and styles will just be
updated on a best-effort basis.
Is that OK?
--
Olivier Certner
next prev parent reply other threads:[~2023-04-26 7:28 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 [this message]
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
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=2624808.XrqEPMHAR6@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).