From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: cschol2112@googlemail.com, lekktu@gmail.com,
mathias.dahl@gmail.com, emacs-devel@gnu.org
Subject: Re: Emacs Windows barebin distribution
Date: Sun, 18 Nov 2012 21:00:04 +0200 [thread overview]
Message-ID: <83lidyzqh7.fsf@gnu.org> (raw)
In-Reply-To: <BA0C75EF69974F4C97888DBB8EC7F1E0@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <lekktu@gmail.com>, <cschol2112@googlemail.com>, <emacs-devel@gnu.org>,
> <mathias.dahl@gmail.com>
> Date: Sun, 18 Nov 2012 10:22:44 -0800
>
> > > If you want to know what users use, ask them.
> >
> > If a feature is broken and no one complains, I can know that without
> > asking.
>
> You are changing the subject. My response to your argument rejecting checking
> the logs was made long before you mentoned that the feature was broken.
Which is exactly the point: time and again you allow yourself to pass
severe judgment on motives of others, without having _any_ idea
whatsoever about the facts of the matter, just because you smell some
"attitude".
If you want your opinions to matter, first learn the subject, or ask.
_Then_ state your opinion, based on facts.
> At that point the discussion was about whether the barebins were being used.
> You had not yet made clear (to my knowledge, at least) that there was anything
> broken wrt barebins.
I assume that people who write their opinions know what they are
talking about. It is your duty to make yourself familiar with facts
before you speak up, especially when talking about something that was
last discussed 7 months ago.
next prev parent reply other threads:[~2012-11-18 19:00 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 [this message]
2012-11-18 17:22 ` Drew Adams
2012-11-18 17:29 ` Juanma Barranquero
2012-11-18 17:39 ` Drew Adams
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=83lidyzqh7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cschol2112@googlemail.com \
--cc=drew.adams@oracle.com \
--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).