From: Eli Zaretskii <eliz@gnu.org>
To: Olivier Certner <ocert.dev@free.fr>
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 12:13:36 +0300 [thread overview]
Message-ID: <83354nuhtr.fsf@gnu.org> (raw)
In-Reply-To: <2624808.XrqEPMHAR6@ravel> (message from Olivier Certner on Wed, 26 Apr 2023 09:28:17 +0200)
> From: Olivier Certner <ocert.dev@free.fr>
> Cc: 63072@debbugs.gnu.org
> Date: Wed, 26 Apr 2023 09:28:17 +0200
>
> > 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.
The "best-effort" part is what bothers me. We introduce these new
styles because the relevant projects change the styles, and then we
basically tell users: don't expect these styles to actually follow
those projects, except by luck? Does that make sense?
next prev parent reply other threads:[~2023-04-26 9:13 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83354nuhtr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63072@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.