From: Eli Zaretskii <eliz@gnu.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 35076@debbugs.gnu.org, stefan@marxist.se
Subject: bug#35076: [26.1] delete-face [FEATURE REQUEST]
Date: Fri, 21 Aug 2020 09:33:01 +0300 [thread overview]
Message-ID: <83lfi8bjaa.fsf@gnu.org> (raw)
In-Reply-To: <20200821033543.q7e7uk3fabtmt6lx@E15-2016.optimum.net> (message from Boruch Baum on Thu, 20 Aug 2020 23:35:43 -0400)
> Date: Thu, 20 Aug 2020 23:35:43 -0400
> From: Boruch Baum <boruch_baum@gmx.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 35076@debbugs.gnu.org
>
> 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.
That is incorrect and unkind. Stefan does a very welcome job (as do
others) of cleaning up forgotten bug reports which received no
attention or whose discussion lapsed. I personally don't always have
time to scan old bug reports and close them, after some initial
communication about it. Stefan and others help by taking care of bug
reports which I failed to handle correctly or timely. I'm infinitely
thankful to them for doing this mundane job, and I think we all should
be grateful. They make the project more successful and our bug DB
cleaner.
As it happens in this case, Stefan interpreted what I meant correctly,
but in the few cases where he misunderstands, I can always speak up
and explain the misunderstanding. And if that means a bug should be
reopened, it takes just one email to do so.
So if you have any objections to closing this bug report, please voice
them, and we will reconsider if necessary.
TIA
next prev parent reply other threads:[~2020-08-21 6:33 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
2020-08-21 6:33 ` Eli Zaretskii [this message]
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=83lfi8bjaa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35076@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
--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).