From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: icon-title-format vs. frame-title-format (Bug#61496)
Date: Thu, 04 May 2023 20:36:47 +0300 [thread overview]
Message-ID: <83y1m4j8wg.fsf@gnu.org> (raw)
In-Reply-To: <87354ccat0.fsf@telefonica.net> (message from Óscar Fuentes on Thu, 04 May 2023 18:37:31 +0200)
> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Thu, 04 May 2023 18:37:31 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Rejecting "___ or minimized" on the docs only works nowadays if the goal
> >> is obfuscating things.
> >
> > We don't reject it. Please, both of you, make a point of actually
> > looking at our manuals before starting argument about problems that
> > don't exist. This is a tempest in a teapot.
>
> I know *we* don't reject it, but the patch submitter was told otherwise
> in an official tone.
He was asked to use one term of the two possible ones, with a reason
behind the request presented as part of it.
> I'm glad that the issue has been clarified. Also, I hope that in the
> future we double-check the project's policies before stating to
> contributors (actual and potential) what's the acceptable way of doing
> things here.
I cannot (and won't) prevent people here from expressing their
opinions, including on terminology. The line between "official tone"
and an opinion of a developer is thin and fine, and is not always
clearly visible, especially when two people are communicating in a
language that isn't the first one for any of them. All I can do is
ask people to take extra care when they express opinions that are not
necessarily codified, as I did in this case more than once.
Eventually, if a contributor was told something they are uncomfortable
with, and wants to know whether it's policy, he or she will have to
ask about that explicitly, and then they will have their answer.
next prev parent reply other threads:[~2023-05-04 17:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 18:40 icon-title-format vs. frame-title-format (Bug#61496) Tobias Bading
2023-05-03 18:56 ` Eli Zaretskii
2023-05-03 19:10 ` Tobias Bading
2023-05-04 0:12 ` Po Lu
2023-05-04 4:03 ` Tobias Bading
2023-05-04 4:38 ` Po Lu
2023-05-04 4:46 ` Tobias Bading
2023-05-04 4:59 ` Tobias Bading
2023-05-04 14:51 ` Óscar Fuentes
2023-05-04 16:08 ` Eli Zaretskii
2023-05-04 16:37 ` Óscar Fuentes
2023-05-04 17:36 ` Eli Zaretskii [this message]
2023-05-05 0:15 ` Po Lu
2023-05-05 1:02 ` Óscar Fuentes
2023-05-05 4:44 ` tomas
2023-05-05 5:33 ` Eli Zaretskii
2023-05-05 7:28 ` tomas
2023-05-05 10:39 ` Eli Zaretskii
2023-05-05 5:24 ` Po Lu
2023-05-05 5:29 ` Eli Zaretskii
2023-05-05 10:40 ` Tobias Bading
2023-05-05 11:00 ` Eli Zaretskii
2023-05-05 11:00 ` Po Lu
2023-05-05 11:17 ` Eli Zaretskii
2023-05-05 12:29 ` Po Lu
2023-05-05 13:31 ` Eli Zaretskii
2023-05-05 23:52 ` Po Lu
2023-05-06 6:27 ` 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=83y1m4j8wg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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).