From: Boruch Baum <boruch_baum@gmx.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 35076@debbugs.gnu.org
Subject: bug#35076: [26.1] delete-face [FEATURE REQUEST]
Date: Thu, 20 Aug 2020 23:35:43 -0400 [thread overview]
Message-ID: <20200821033543.q7e7uk3fabtmt6lx@E15-2016.optimum.net> (raw)
In-Reply-To: <CADwFkmkoM3Hm-RtaNKbuF9ED78c4Jy5CntWKudPqzTqeaD66Uw@mail.gmail.com>
Suddenly Eli can't speak or act for himself? If within the GNU project
you're his manager or his superior, great then I see nothing wrong in
your intervention on his behalf. I just don't understand enough about
how the project is organized. From the limited e-mail traffic I receive,
it seems that Eli's task is mainly to remove bugs and deficiencies from
emacs by producing, and that your's is mainly to remove bugs and
deficiencies from emacs by just closing them.
On 2020-08-20 19:09, Stefan Kangas wrote:
> The above quote by Eli makes it clear that we would need a very good
> reason to do something like this. It seems like we are missing that
> here, and no further details have been given within over a year.
>
> I'm therefore closing this bug report as wontfix.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
next prev parent reply other threads:[~2020-08-21 3:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 0:04 bug#35076: [26.1] delete-face [FEATURE REQUEST] Boruch Baum
2019-04-02 0:15 ` Basil L. Contovounesios
2019-04-02 0:38 ` Boruch Baum
2019-04-02 15:10 ` Eli Zaretskii
2019-04-02 14:33 ` Eli Zaretskii
2020-08-21 2:09 ` Stefan Kangas
2020-08-21 3:35 ` Boruch Baum [this message]
2020-08-21 6:33 ` Eli Zaretskii
2020-08-21 8:17 ` Boruch Baum
[not found] <<20190402000403.rb3cb4b6tzqys4vy@E15-2016.optimum.net>
[not found] ` <<8336n0h3yp.fsf@gnu.org>
2019-04-02 15:03 ` Drew Adams
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=20200821033543.q7e7uk3fabtmt6lx@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--cc=35076@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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).