From: "Erik K." <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Aw: New DNS-forwarding wiki
Date: Mon, 29 Jul 2013 18:17:39 +0200 [thread overview]
Message-ID: <A1626B39-D378-4C72-B6F7-5C555D8A04BE@ipfire.org> (raw)
In-Reply-To: <trinity-0d5119f5-c138-4858-9edf-ae40a351e434-1375100190403@3capp-gmx-bs31>
[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]
Hi Thomas,
thanks for the response.
> The wiki workflow-overview is realy great! this will create the fast and uncontrolled clearly difficult. :)
Hope so.
Might be nice if someone can also go for some english checks.
Greetings
Erik
Am 29.07.2013 um 14:16 schrieb t.berthel(a)gmx.net:
> Hi Erik,
>
>> please go for enhancements. Otherwise point (C) can be worked out.
> my englisch is not the best, but the technical information in the topic are right.
>
> The wiki workflow-overview is realy great! this will create the fast and uncontrolled clearly difficult. :)
>
> greetings, Thomas
>
> Gesendet: Montag, 29. Juli 2013 um 12:24 Uhr
> Von: "Erik K." <ummeegge(a)ipfire.org>
> An: "Mailingliste IPFire" <documentation(a)lists.ipfire.org>
> Betreff: New DNS-forwarding wiki
>
> Dear documentation team,
> i want to introduce the DNS-forwarding wiki http://wiki.ipfire.org/en/configuration/network/dnsforward
> which was extended and is currently on stage (B) of the new wiki workflow --> http://wiki.ipfire.org/projects/docs/workflow[http://wiki.ipfire.org/projects/docs/workflow] .
>
> If you think the point "(B) Authoring the article in English" lacks, please go for enhancements. Otherwise point (C) can be worked out.
>
>
> Greetings
>
> Erik
prev parent reply other threads:[~2013-07-29 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <62196ED5-50F8-47F5-83E7-E05A8F25BE35@ipfire.org>
2013-07-29 12:16 ` t.berthel
2013-07-29 16:17 ` Erik K. [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=A1626B39-D378-4C72-B6F7-5C555D8A04BE@ipfire.org \
--to=ummeegge@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