From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 45806@debbugs.gnu.org
Subject: bug#45806: 26.3; `menu-bar-separator'
Date: Tue, 12 Jan 2021 20:23:14 +0200 [thread overview]
Message-ID: <83pn2ac8vh.fsf@gnu.org> (raw)
In-Reply-To: <8ba18d55-3484-4186-b8c2-0335cd8b7b7c@default> (message from Drew Adams on Tue, 12 Jan 2021 10:09:08 -0800 (PST))
> Date: Tue, 12 Jan 2021 10:09:08 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 45806-done@debbugs.gnu.org
>
> > Why am I not surprised that you don't accept the judgment of the
> > project maintainers?
>
> Why am I not surprised that you are personally
> hostile, and interpret an opinion as non-acceptance
> of a decision?
You expressed your opinion, heard its rejection, but you keep arguing.
That generates more messages than necessary and increase the workload
for no good reason, while telling nothing new. Why increase the noise
level here?
> Can we not politely agree to disagree about what
> should be done
We can, but one message from each side should be enough for that.
There should be no need for "I heard you, but I still disagree". It's
a waste of time and energy.
next prev parent reply other threads:[~2021-01-12 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<73e90890-b70a-4eb8-aa9e-d40959d1e1ec@default>
[not found] ` <<83pn2adwn1.fsf@gnu.org>
2021-01-12 16:34 ` bug#45806: 26.3; `menu-bar-separator' Drew Adams
2021-01-12 17:03 ` Eli Zaretskii
2021-01-12 18:09 ` Drew Adams
2021-01-12 18:22 ` Eli Zaretskii
2021-01-12 18:23 ` Eli Zaretskii [this message]
2021-01-12 0:32 Drew Adams
2021-01-12 15:04 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pn2ac8vh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45806@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.