From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: rms@gnu.org, emacs-devel@gnu.org, stephen_leake@stephe-leake.org
Subject: Re: master 31945b6c3f: * lisp/progmodes/eglot.el (eglot): Ensure managed-major-mode is a list
Date: Fri, 28 Oct 2022 14:30:02 +0300 [thread overview]
Message-ID: <83fsf8jidh.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm52XUtF2Hbyn5QvJncF=tDgJRXGP8MAprws4hX2yEjVP=w@mail.gmail.com> (message from João Távora on Fri, 28 Oct 2022 09:32:08 +0100)
> From: João Távora <joaotavora@gmail.com>
> Date: Fri, 28 Oct 2022 09:32:08 +0100
> Cc: rms@gnu.org, emacs-devel@gnu.org, stephen_leake@stephe-leake.org
>
> It's just that my (and seemingly Richard's) preference is a little more
> lax. If something is definitely off cosmetically (say, very long lines
> or misleadingly hard to read indentation), then a separate commit
> that targets those cosmetics shortcomings is acceptable.
I'm okay with your preferences in the package for whose maintenance
you are responsible. But people who read this list should be aware of
our project-wide preferences, lest they somehow interpret what you and
Richard say as what they need to follow in general. This list is read
by many people, not just the three of us.
next prev parent reply other threads:[~2022-10-28 11:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166668943749.31970.9379739764487638921@vcs2.savannah.gnu.org>
[not found] ` <20221025091717.DD9A3C0E4BF@vcs2.savannah.gnu.org>
2022-10-25 9:29 ` master 31945b6c3f: * lisp/progmodes/eglot.el (eglot): Ensure managed-major-mode is a list João Távora
2022-10-25 9:35 ` João Távora
2022-10-27 20:13 ` Richard Stallman
2022-10-28 5:42 ` Eli Zaretskii
2022-10-28 8:32 ` João Távora
2022-10-28 11:30 ` Eli Zaretskii [this message]
2022-10-28 19:45 ` Stefan Kangas
2022-10-29 5:56 ` Eli Zaretskii
2022-10-29 6:52 ` Stefan Kangas
2022-10-29 7:24 ` Eli Zaretskii
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=83fsf8jidh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=rms@gnu.org \
--cc=stephen_leake@stephe-leake.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).