emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Allen Li <vianchielfaura@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: [IMPORTANT] Server migration: please update your git repositories before 31/12/2017
Date: Sat, 30 Dec 2017 13:50:03 -0800	[thread overview]
Message-ID: <CAJr1M6efNDmPgTvazryF3dupR0HptGjA7aHgH9sS6d4b-g6fAg@mail.gmail.com> (raw)
In-Reply-To: <87d12w77i4.fsf@gnu.org>

On Sat, Dec 30, 2017 at 3:57 AM, Bastien <bzg@gnu.org> wrote:
> Hi Achim,
>
> Achim Gratz <Stromeko@Nexgo.DE> writes:
>
>> Am 29.12.2017 um 13:26 schrieb Bastien Guerry:
>>> Migrating to a new vultr instance was easier than trying to upgrade
>>> the rackspace hosting service and the vultr pricing is better.
>>
>> It's water under the bridge now, but if there had been a discussion
>> here we might have converged to a different solution.
>
> Yes, I should have raised the issue on the list to see if people would
> come up with preferrable solutions, apologies for that.
>
> But I had very little time and the clock was ticking.
>
> Since I wasn't sure I could follow a potentially long discussion with
> many suggestions, and since the solution I envisioned does not impact
> regular users, I thought it was best to *just do it*.
>
> Nothing is irreversible, my time is gone anyway.
>
> So if you want to open a discussion on better hosting plans and if you
> or someone else is willing to handle the migration and to maintain the
> server afterwards, we can of course discuss this.

It sounds like we already have a solution, so I don't suggest anyone
spend more time on this since I am sure there are lots of bugs that
would be worth fixing.

I don’t want to blame anyone, just to clarify the state of affairs.  It
looks like Rackspace failed to communicate properly and on short notice.
People simply make mistakes, including myself, so I don’t think pointing
fingers is productive.

  reply	other threads:[~2017-12-30 21:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-28 17:12 [IMPORTANT] Server migration: please update your git repositories before 31/12/2017 Bastien Guerry
2017-12-29  7:32 ` Michael Welle
2017-12-29 12:23   ` Bastien Guerry
2017-12-29  9:59 ` Achim Gratz
2017-12-29 12:26   ` Bastien Guerry
2017-12-30 10:39     ` Allen Li
2017-12-30 11:23       ` Bastien
2017-12-30 11:39     ` Achim Gratz
2017-12-30 11:57       ` Bastien
2017-12-30 21:50         ` Allen Li [this message]
2017-12-31  8:53         ` Achim Gratz
2017-12-29 16:43 ` Bastien Guerry
2018-01-04 18:11   ` Achim Gratz
2018-01-04 18:44     ` Kaushal Modi
2018-01-04 18:50       ` Nicolas Goaziou
2018-01-04 18:52         ` Kaushal Modi
2018-01-05 17:31           ` Kaushal Modi
2018-01-05 17:47             ` Probably broke the Worg build? (Was: Re: [IMPORTANT] Server migration..) Kaushal Modi
2018-01-06  1:54               ` Probably broke the Worg build? Bastien
2018-01-06  2:05                 ` Kaushal Modi
2018-01-06  2:54                   ` Kaushal Modi
2018-01-04 19:21       ` [IMPORTANT] Server migration: please update your git repositories before 31/12/2017 Achim Gratz
2018-01-04 14:19 ` Kaushal Modi
2018-01-04 15:36   ` Nicolas Goaziou
2018-01-04 16:05     ` Kaushal Modi
2018-01-04 18:12       ` Nicolas Goaziou

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.orgmode.org/

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

  git send-email \
    --in-reply-to=CAJr1M6efNDmPgTvazryF3dupR0HptGjA7aHgH9sS6d4b-g6fAg@mail.gmail.com \
    --to=vianchielfaura@gmail.com \
    --cc=Stromeko@nexgo.de \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@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/org-mode.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).