unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Daniel Fleischer <danflscr@gmail.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: [PATCH] Package Installation in Tutorial
Date: Sat, 4 Dec 2021 17:38:53 +0000	[thread overview]
Message-ID: <SJ0PR10MB54881D7E6E4392A27DF2FA7EF36B9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <835ys47pzx.fsf@gnu.org>

> > > I'm again asking what _you_ look to, as evidence
> > > that installing & deleting packages is something
> > > that first-timers really need, as part of our
> > > learn-by-doing tutorial.
> >
> > I feel like that's not fair. In the short time I've been here I was able
> > to see features being implemented which were NOT backed up by any
> > external data or polls (discussions here are not included). Moreover,
> > some updates were motivated by individual bug reports which is a sample
> > of one.
> 
> Drew doesn't speak for the Emacs project, so don't be surprised when
> his views contradict the project's practices and decision-making
> process.  He (consistently) opposes those as well.

Here we go again, with another of Eli's knee-jerk
ad hominem attacks.

Asking for reasons for making a proposed change
is not a contradiction of the Emacs project's
practices or decision-making process.  And no,
Drew does not oppose those, consistently or
otherwise.

Progress is not incompatible with disagreeing
about a given decision or proposal.

And discussing reasons & counter-reasons that
back up arguments and proposals, is no threat
to progress.  Quite the opposite.

Appeal to authority as an argument is weak,
even if sometimes legitimate.  When it's the
only reason given, that's sad.



  parent reply	other threads:[~2021-12-04 17:38 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 17:30 [PATCH] Package Installation in Tutorial Daniel Fleischer
2021-12-01 18:06 ` Daniel Martín
2021-12-01 19:25   ` Stefan Kangas
2021-12-01 19:25 ` Stefan Kangas
2021-12-02  6:42   ` Daniel Fleischer
2021-12-02  9:09   ` Juri Linkov
2021-12-02 11:17     ` Stefan Kangas
2021-12-03  6:57       ` Daniel Fleischer
2021-12-03 16:29         ` [External] : " Drew Adams
2021-12-03 17:48           ` Daniel Fleischer
2021-12-03 18:53             ` Stefan Kangas
2021-12-03 18:56               ` Drew Adams
2021-12-03 18:53             ` Drew Adams
2021-12-03 19:24               ` Stefan Kangas
2021-12-03 20:24                 ` Drew Adams
2021-12-03 22:54                   ` Stefan Kangas
2021-12-03 21:19               ` Daniel Fleischer
2021-12-03 23:01                 ` Drew Adams
2021-12-04  8:06                 ` Eli Zaretskii
2021-12-04 11:04                   ` Daniel Fleischer
2021-12-04 18:16                     ` Drew Adams
2021-12-04 21:06                       ` Daniel Fleischer
2021-12-04 17:38                   ` Drew Adams [this message]
2021-12-04  5:44               ` Richard Stallman
2021-12-04  8:04                 ` Eli Zaretskii
2021-12-04 17:20                   ` Drew Adams
2021-12-04 17:18                 ` Drew Adams
2021-12-03 17:00         ` Lars Ingebrigtsen
2021-12-04 13:08           ` Stefan Kangas
2021-12-04 14:15             ` Daniel Fleischer
2021-12-04 16:29               ` Eli Zaretskii
2021-12-04 20:38                 ` Daniel Fleischer
2021-12-04 21:58                   ` Lars Ingebrigtsen
2021-12-05  9:37                     ` Daniel Fleischer
2021-12-05 20:52                       ` Lars Ingebrigtsen
2021-12-05 10:21                   ` Eli Zaretskii
2021-12-05 10:54                     ` Daniel Fleischer
2021-12-05 11:44                       ` Stefan Kangas
2021-12-05 15:33                         ` Daniel Fleischer
2021-12-06 10:36                           ` Daniel Fleischer
2021-12-06 14:10                           ` Stefan Kangas
2021-12-05 11:29                     ` Stefan Kangas

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=SJ0PR10MB54881D7E6E4392A27DF2FA7EF36B9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=danflscr@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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).