From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juanma Barranquero'" <lekktu@gmail.com>
Cc: cschol2112@googlemail.com, 'Eli Zaretskii' <eliz@gnu.org>,
emacs-devel@gnu.org, 'Mathias Dahl' <mathias.dahl@gmail.com>
Subject: RE: Emacs Windows barebin distribution
Date: Sun, 18 Nov 2012 09:39:37 -0800 [thread overview]
Message-ID: <B3429F66EF70428DABF8B34E79C3F480@us.oracle.com> (raw)
In-Reply-To: <CAAeL0SSJHvLbSNXmtDZObrJqQ+N4=u7+KeqRmA80iuy+kQLv6Q@mail.gmail.com>
> > And in this case a very good measure was proposed. And,
> > unbelievably, it was summarily dismissed/countered in
> > favor of reliance on the much poorer measure of
> > emacs-devel activity. That is the argument and the
> > attitude I spoke out against.
>
> Polling users doesn't happen on its own. Someone has to spend the time
> to do it.
The proposal from Matthias was not a proposal to poll the users. He suggested
examining the download logs to see how much the barebins were picked up.
I do not know how much energy is required to do that, which is why my support
for it was qualified by "if easy", "if feasible" etc.
> Removing something deemed unnecessary and waiting for anyone
> to complain is less work. That wouldn't be a good rationale for
> killing a heavily used, or a core, feature, but it seems perfectly
> reasonable to me when speaking of something that's likely not used by
> anybody (more so after Eli's comment about it being broken).
I don't disagree with that at all. I agree that it is a reasonable approach.
My argument was against the reasoning that _because_ no one has spoken up here
there must not be any user interest in this. That's a false argument and
suggests a bad attitude, IMHO.
> So the argument and the attitude is, I think, "why should we spend
> time in something that we're convinced it is useless anyway, unless we
> have a good reason to think otherwise?"
See above. That is a fair argument. But that is not the argument and attitude
I was speaking about.
next prev parent reply other threads:[~2012-11-18 17:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 14:28 Emacs Windows barebin distribution Christoph Scholtes
2012-04-15 16:18 ` Eli Zaretskii
2012-11-16 22:48 ` Dani Moncayo
2012-11-16 22:54 ` Dani Moncayo
2012-11-17 7:50 ` Eli Zaretskii
2012-11-17 8:27 ` Dani Moncayo
2012-11-17 8:56 ` Eli Zaretskii
2012-11-18 12:52 ` Mathias Dahl
2012-11-18 15:30 ` Eli Zaretskii
2012-11-18 15:50 ` Drew Adams
2012-11-18 16:20 ` Juanma Barranquero
2012-11-18 17:12 ` Eli Zaretskii
2012-11-18 17:37 ` Drew Adams
2012-11-18 17:55 ` Eli Zaretskii
2012-11-18 18:22 ` Drew Adams
2012-11-18 19:00 ` Eli Zaretskii
2012-11-18 17:22 ` Drew Adams
2012-11-18 17:29 ` Juanma Barranquero
2012-11-18 17:39 ` Drew Adams [this message]
2012-11-18 17:45 ` Juanma Barranquero
2012-11-18 18:22 ` Drew Adams
2012-11-19 4:02 ` Stephen J. Turnbull
2012-11-18 17:36 ` Eli Zaretskii
2012-11-20 13:58 ` Jason Rumney
2012-11-21 4:23 ` Stephen J. Turnbull
2012-11-18 19:56 ` Mathias Dahl
2012-11-18 20:22 ` Dani Moncayo
2012-11-18 20:45 ` Dani Moncayo
2012-11-18 21:28 ` Eli Zaretskii
2012-11-18 21:14 ` Eli Zaretskii
2012-04-15 16:43 ` Jambunathan K
2012-04-16 0:02 ` 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=B3429F66EF70428DABF8B34E79C3F480@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=cschol2112@googlemail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=mathias.dahl@gmail.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 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).