From: Carlos O'Donell <carlos@redhat.com>
To: "Frank Ch. Eigler" <fche@elastic.org>,
overseers@sourceware.org, Florian Weimer <fweimer@redhat.com>
Subject: Re: Choice of distribution for new sourceware.org server?
Date: Thu, 06 Feb 2020 01:51:00 -0000 [thread overview]
Message-ID: <d78cfd56-7434-c917-0344-9e232b4a0494@redhat.com> (raw)
In-Reply-To: <20200206013405.GC97355@elastic.org>
On 2/5/20 8:34 PM, Frank Ch. Eigler wrote:
> Hi -
>
>> I have suggested Fedora in the past and would be happy to be using it.
>
> Having to upgrade apprx. every 8 months is a PITA though, with so much
> activity and non-distro software on the machine.
Sorry, I don't follow, could you expand on this a bit?
How much non-distro software is there on sourceware?
When you say "activity" do you mean that users would be impacted once
every 8 months for a small window of downtime?
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-02-06 1:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 1:05 Carlos O'Donell
2020-02-06 1:30 ` Christopher Faylor
2020-02-06 1:34 ` Frank Ch. Eigler
2020-02-06 1:51 ` Carlos O'Donell [this message]
2020-02-06 2:02 ` Frank Ch. Eigler
2020-02-06 2:16 ` Carlos O'Donell
2020-02-06 14:49 ` Frank Ch. Eigler
2020-02-06 15:10 ` Carlos O'Donell
2020-02-06 15:19 ` Frank Ch. Eigler
2020-02-06 16:36 ` Carlos O'Donell
2020-02-06 16:46 ` Christopher Faylor
2020-02-06 16:49 ` Frank Ch. Eigler
2020-02-06 1:45 ` Carlos O'Donell
2020-02-06 6:05 ` Christopher Faylor
2020-02-06 14:50 ` Carlos O'Donell
2020-02-06 15:11 ` Lukas Berk
2020-02-06 15:22 ` Carlos O'Donell
2020-02-06 15:20 ` Christopher Faylor
2020-02-06 17:05 ` Carlos O'Donell
2020-02-06 18:28 ` Joseph Myers
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=d78cfd56-7434-c917-0344-9e232b4a0494@redhat.com \
--to=carlos@redhat.com \
--cc=fche@elastic.org \
--cc=fweimer@redhat.com \
--cc=overseers@sourceware.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.
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).