From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Old items on IPFire Wiki
Date: Tue, 30 Jul 2019 16:51:51 +0100 [thread overview]
Message-ID: <0255E782-4F1F-4879-BD3D-3F064857B8A7@ipfire.org> (raw)
In-Reply-To: <2C6CF0AC-782D-4EBA-86BE-9BE92B2D0620@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1694 bytes --]
Hi,
So, to follow up with you guys on here…
I had to move the wiki. We lost the converter so I had to work based off of what we have right now.
This is not at all a drama. It makes things a little bit easier actually.
The new wiki is online now and I think it works okay. There might be some more bugs, please report them to BZ as usual.
There is now a lot of broken links to fix and some other broken syntax. It would be nice to get some help with that.
I added a syntax reference which I think will be very helpful for this.
Best,
-Michael
> On 25 Jul 2019, at 20:11, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>
>
> Found something wrong. The wiki search is not working for me (Mac Safari current version). Maybe it is indexing?
>
>
>> From: Jon Murphy
>> Sent: Thursday, July 25, 2019, 1:38 PM
>> To: Michael Tremer; documentation(a)lists.ipfire.org
>> Subject: Re: Old items on IPFire Wiki
>>
>>
>> All looks good! Thank you!
>>
>>>
>>> Hey Jon,
>>>
>>> Very interesting. I did not even notice this.
>>>
>>> I am restoring the backup now. Nothing is lost.
>>>
>>> Could you please double-check for me?
>>>
>>> Best,
>>> -Michael
>>>
>>>> On 24 Jul 2019, at 18:27, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>>>>
>>>> Michael,
>>>>
>>>> It looks like the current IPFire wiki is from 2018. Many of the recently added articles are missing.
>>>>
>>>> From the July 19 IPFire twitter post it looks like there were issues getting the new system online. So I apologize if this is already know.
>>>>
>>>> Could an update be sent out via twitter or via the blog?
>>>>
>>>> Thank you!
>>>> Jon
>>>
>>
>
next parent reply other threads:[~2019-07-30 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2C6CF0AC-782D-4EBA-86BE-9BE92B2D0620@gmail.com>
2019-07-30 15:51 ` Michael Tremer [this message]
2019-07-24 17:27 Jon Murphy
2019-07-25 13:08 ` Michael Tremer
2019-07-25 18:38 ` Jon Murphy
2019-07-25 18:57 ` 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=0255E782-4F1F-4879-BD3D-3F064857B8A7@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=documentation@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