all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Van L <van@scratch.space>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
	Emacs-Devel devel <emacs-devel@gnu.org>,
	20202@debbugs.gnu.org, 20484@debbugs.gnu.org,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Phillip Lord <phillip.lord@russet.org.uk>
Subject: Re: EMACS=t Joy and Happiness
Date: Fri, 25 May 2018 08:11:25 +0200	[thread overview]
Message-ID: <87fu2gb6ya.fsf@elephly.net> (raw)
In-Reply-To: <D5C20BA1-A158-4A79-851A-7C57EBB58868@scratch.space>


Van L <van@scratch.space> writes:

>> Paul Eggert writes:
>>
>> this is the most recent RHEL available
>
> You could have your sclerotic institution’s IT manager provide
> Enterprise RHEL for students studying topics as old as the hills and
> mountains (and they won’t change) and request them to “think" about
> the latest unstable Fedora or Debian or Ubuntu releases for research
> oriented experimental AI & CS “work” which are hot career topics and
> ought not to be held back by bureaucratically convenient RHEL IT
> hell. Ask them for what Tesla or Uber or Facebook or Google use to
> keep up with “innovation” before it is "too late" on RHEL.

This is not constructive.

There are even RHEL 6 deployments out there, because it’s still
supported until 2020.  There are people who pay for the privilege of not
having to upgrade.

--
Ricardo





  parent reply	other threads:[~2018-05-25  6:11 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 20:46 EMACS=t Joy and Happiness Phillip Lord
2018-05-24 20:52 ` bug#20202: " Stefan Monnier
2018-05-24 20:52 ` Stefan Monnier
2018-05-24 22:03 ` bug#20484: " Paul Eggert
2018-05-24 22:03 ` Paul Eggert
2018-05-25  2:25   ` bug#20202: " Van L
2018-05-25  6:11     ` Ricardo Wurmus
2018-05-25  6:11     ` bug#20484: " Ricardo Wurmus
2018-05-25  6:11     ` Ricardo Wurmus [this message]
2018-05-25  7:12       ` Van L
2018-05-25 17:59     ` bug#20484: " Paul Eggert
2018-05-25 17:59     ` bug#20202: " Paul Eggert
2018-05-25 17:59     ` Paul Eggert
2018-05-26  0:17       ` Van L
2018-05-26  7:41         ` Eli Zaretskii
2018-05-26 10:07           ` Van L
2018-05-26 10:57             ` Eli Zaretskii
2018-05-26  0:43       ` Van L
2018-05-25  6:16   ` bug#20202: " Eli Zaretskii
2018-05-25  6:16   ` Eli Zaretskii
2018-05-25  7:28     ` bug#20484: " Van L
2018-05-25  7:28     ` bug#20202: " Van L
2018-05-25  7:28     ` Van L
2018-05-25  8:02       ` bug#20484: " Eli Zaretskii
2018-05-25  8:02       ` Eli Zaretskii
2018-05-26  0:01         ` Van L
2018-05-25  8:02       ` bug#20202: " Eli Zaretskii
2018-05-25 17:50     ` Paul Eggert
2018-05-25  6:16   ` bug#20484: " Eli Zaretskii
2018-05-25 22:34   ` Phillip Lord
2018-05-24 22:03 ` bug#20202: " Paul Eggert
2018-05-25 20:36 ` Paul Eggert
2018-05-25 20:36 ` bug#20484: " Paul Eggert
2018-05-25 20:36 ` Paul Eggert
2018-05-25 22:49   ` bug#20202: " Phillip Lord
2018-05-26  7:20   ` bug#20484: " Eli Zaretskii
2018-05-26 20:54     ` bug#20202: " Paul Eggert
2018-05-26 20:54     ` bug#20484: " Paul Eggert
2018-05-26 20:54     ` Paul Eggert
2018-05-31 21:07       ` bug#20202: " Phillip Lord
2018-05-31 23:45         ` Paul Eggert
2018-05-31 23:45         ` bug#20484: " Paul Eggert
2018-05-31 23:45         ` Paul Eggert
2018-06-01  1:56           ` Stefan Monnier
2018-06-01  1:56           ` bug#20484: " Stefan Monnier
2018-06-01  1:56           ` bug#20202: " Stefan Monnier
2018-06-01  7:04           ` bug#20484: " Eli Zaretskii
2018-06-01  7:04           ` bug#20202: " Eli Zaretskii
2018-06-01  7:04           ` Eli Zaretskii
2018-06-01 14:08             ` bug#20202: " Paul Eggert
2018-06-01 14:08             ` bug#20484: " Paul Eggert
2018-06-01 14:08             ` Paul Eggert
2018-06-01 14:14               ` bug#20484: " Eli Zaretskii
2018-06-14 20:54                 ` bug#20202: " Paul Eggert
2018-06-14 20:54                 ` Paul Eggert
2018-06-14 20:54                 ` bug#20484: " Paul Eggert

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fu2gb6ya.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=20202@debbugs.gnu.org \
    --cc=20484@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=phillip.lord@russet.org.uk \
    --cc=van@scratch.space \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.