all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Van L <van@scratch.space>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: EMACS=t Joy and Happiness
Date: Sat, 26 May 2018 20:07:42 +1000	[thread overview]
Message-ID: <ACB351DC-A549-476A-A18B-0F45FD09AF99@scratch.space> (raw)
In-Reply-To: <83y3g6984k.fsf@gnu.org>


> On 26 May 2018, at 17:41, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Van L <van@scratch.space>
>> Date: Sat, 26 May 2018 10:17:02 +1000
>> Cc: Emacs-Devel devel <emacs-devel@gnu.org>
>> 
>> I was upset by the idea of paying more to not upgrade.
> 
> I guess you never had the experience of upgrading a system in a
> production-type environments, with a large number of users, each of
> whom has their specific requirements and packages that need to
> continue running smoothly.

Let’s not get personal.

This is about the system and upgrades.

Anyway, it is now the law to report a breach within 72-hours or pay 4% of revenue.

Your are skating over a concept large installations use orchestration toolchains for devopsproding.




  reply	other threads:[~2018-05-26 10:07 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 ` Paul Eggert
2018-05-25  2:25   ` bug#20202: " Van L
2018-05-25  6:11     ` Ricardo Wurmus
2018-05-25  7:12       ` Van L
2018-05-25  6:11     ` bug#20484: " Ricardo Wurmus
2018-05-25  6:11     ` bug#20202: " Ricardo Wurmus
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 [this message]
2018-05-26 10:57             ` Eli Zaretskii
2018-05-26  0:43       ` Van L
2018-05-25 17:59     ` bug#20202: " Paul Eggert
2018-05-25 17:59     ` bug#20484: " Paul Eggert
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     ` 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  7:28     ` Van L
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 ` Paul Eggert
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     ` Paul Eggert
2018-05-31 21:07       ` bug#20202: " Phillip Lord
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#20202: " Stefan Monnier
2018-06-01  1:56           ` bug#20484: " Stefan Monnier
2018-06-01  7:04           ` bug#20202: " Eli Zaretskii
2018-06-01  7:04           ` bug#20484: " Eli Zaretskii
2018-06-01  7:04           ` Eli Zaretskii
2018-06-01 14:08             ` Paul Eggert
2018-06-01 14:14               ` bug#20484: " Eli Zaretskii
2018-06-14 20:54                 ` Paul Eggert
2018-06-14 20:54                 ` Paul Eggert
2018-06-14 20:54                 ` bug#20202: " Paul Eggert
2018-06-01 14:08             ` Paul Eggert
2018-06-01 14:08             ` bug#20484: " Paul Eggert
2018-05-31 23:45         ` bug#20202: " Paul Eggert
2018-05-26 20:54     ` bug#20484: " Paul Eggert
2018-05-26 20:54     ` bug#20202: " 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=ACB351DC-A549-476A-A18B-0F45FD09AF99@scratch.space \
    --to=van@scratch.space \
    --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 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.