From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Access to IPFire pages
Date: Tue, 02 Feb 2021 10:22:44 +0100 [thread overview]
Message-ID: <fe4aed87-ab74-431f-9933-c2c134cca3c5@ipfire.org> (raw)
In-Reply-To: <trinity-fe111915-d6b6-4ca1-9075-a3d1602ff6ed-1612255153025@3c-app-gmx-bs73>
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
On 02.02.2021 09:39, Bernhard Bitsch wrote:
> Hi,
Hi Bernhard,
> at the moment I can't access people.ipfire.org, blog.ipfire.ord, wiki.ipfire.org.
10:19 o'clock => I just tested all three - all working.
> Is there a problem?
If there was: its fixed. If you still have no access, there could be
another problem. Perhaps you get blocked as me a few days ago?
HTH,
Matthias
next prev parent reply other threads:[~2021-02-02 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 8:39 Bernhard Bitsch
2021-02-02 9:22 ` Matthias Fischer [this message]
2021-02-02 10:47 ` Michael Tremer
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=fe4aed87-ab74-431f-9933-c2c134cca3c5@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.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