From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: eggert@cs.ucla.edu, 26102@debbugs.gnu.org, hengaini2055@qq.com
Subject: bug#26102: movemail can't connect mail server
Date: Thu, 16 Mar 2017 17:33:03 +0200 [thread overview]
Message-ID: <83var9z174.fsf@gnu.org> (raw)
In-Reply-To: <ls1stykrg9.fsf@fencepost.gnu.org> (message from Glenn Morris on Wed, 15 Mar 2017 20:15:02 -0400)
> From: Glenn Morris <rgm@gnu.org>
> Cc: eggert@cs.ucla.edu, hengaini2055@qq.com, 26102@debbugs.gnu.org
> Date: Wed, 15 Mar 2017 20:15:02 -0400
>
> I want to point out that answering (or reading) this bug report (and the
> previous help-gnu-emacs post) is an act that takes maintainer time,
> therefore the maintenance cost is not zero.
It's zero as in "negligible", since the time it took to understand the
cockpit errors was short, and it's not like questions about movemail
get posted frequently (I don't remember any for a long time).
Neither did I see anyone from the developers group besides myself
interested in answering the question, as long as the actual problem
was on the table.
> (Obviously Paul and I have increased the short-term cost by starting a
> discussion
Indeed.
> And when anyone needs to read (whether or not they change it) the
> relevant support code in rmail or lib-src/Makefile, that's a cost too.
> Yes, the cost is very small, but these things add up over time.
>
> We clearly don't have enough people to maintain the code we have.
> So personally I'm pro-simplification
In general, so am I. But this particular bike shed is not worth
wasting time on.
prev parent reply other threads:[~2017-03-16 15:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 1:14 bug#26102: movemail can't connect mail server �ž��
2017-03-15 15:49 ` Eli Zaretskii
2017-03-15 17:30 ` Paul Eggert
2017-03-15 17:48 ` Eli Zaretskii
2017-03-15 18:15 ` Glenn Morris
2017-03-15 18:20 ` Eli Zaretskii
2017-03-15 20:03 ` Noam Postavsky
2017-03-16 3:31 ` Eli Zaretskii
2017-03-15 22:48 ` Paul Eggert
2017-03-16 15:31 ` Eli Zaretskii
2017-03-17 7:23 ` Paul Eggert
2017-03-17 8:58 ` Eli Zaretskii
2017-03-17 10:49 ` Lars Ingebrigtsen
2017-03-17 10:56 ` Eli Zaretskii
2017-03-16 0:15 ` Glenn Morris
2017-03-16 15:33 ` Eli Zaretskii [this message]
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=83var9z174.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26102@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=hengaini2055@qq.com \
--cc=rgm@gnu.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).