From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/2] README.md: update text & adjust links to new URLs
Date: Thu, 28 Mar 2024 10:32:56 +0000 [thread overview]
Message-ID: <60BC4E3F-0ECD-4B7B-B0B5-A010618D5EBA@ipfire.org> (raw)
In-Reply-To: <20240328095152.2391304-1-rico.hoppe@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1840 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
Thank you. Congratulations to your first patch :)
> On 28 Mar 2024, at 09:51, Rico Hoppe <rico.hoppe(a)ipfire.org> wrote:
>
> - links for: about, documentation, help
> - wording: wiki to documentation
>
> Signed-off-by: Rico Hoppe <rico.hoppe(a)ipfire.org>
> ---
> README.md | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/README.md b/README.md
> index df3d35717..5e88d31dd 100644
> --- a/README.md
> +++ b/README.md
> @@ -4,7 +4,7 @@
>
> IPFire is a hardened, versatile, state-of-the-art Open Source firewall based on
> Linux. Its ease of use, high performance in any scenario and extensibility make
> -it usable for everyone. For a full list of features have a look [here](https://www.ipfire.org/features).
> +it usable for everyone. For a full list of features have a look [here](https://www.ipfire.org/about).
>
> This repository contains the source code of IPFire 2.x which is used to build
> the whole distribution from scratch, since IPFire is not based on any other
> @@ -16,13 +16,13 @@ Just head over to https://www.ipfire.org/download
>
> # How do I use this software?
>
> -We have a long and detailed wiki located [here](https://wiki.ipfire.org/) which
> +We have a long and detailed documentation located [here](https://ipfire.org/docs) which
> should answers most of your questions.
>
> # But I have some questions left. Where can I get support?
>
> You can ask your question at our community located [here](https://community.ipfire.org/).
> -A complete list of our support channels can be found [here](https://www.ipfire.org/support).
> +A complete list of our support channels can be found [here](https://www.ipfire.org/help).
>
> # How can I contribute?
>
> --
> 2.39.2
>
prev parent reply other threads:[~2024-03-28 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 9:51 Rico Hoppe
2024-03-28 9:51 ` [PATCH 2/2] README.md: fix minor typo Rico Hoppe
2024-03-28 10:33 ` Michael Tremer
2024-03-28 10:32 ` Michael Tremer [this message]
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=60BC4E3F-0ECD-4B7B-B0B5-A010618D5EBA@ipfire.org \
--to=michael.tremer@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