From: "Daniel Weismüller" <whytea@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] Antw.: New documentation for new addons
Date: Mon, 09 Jul 2012 11:47:54 +0200 [thread overview]
Message-ID: <4FFAA8CA.1040906@ipfire.org> (raw)
In-Reply-To: <1341824129.31350.14.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 4468 bytes --]
hmm ok i'll do that
Am 09.07.2012 10:55, schrieb Michael Tremer:
> Yes, I think we could do that. Please open me a bug report and I will do
> that as soon as possible.
>
> Will you do the documentation then?
>
> Michael
>
> On Mon, 2012-07-09 at 10:50 +0200, Daniel Weismüller wrote:
>> What about the telnet addon is there a way to bring it to stable too?
>>
>> Am 09.07.2012 10:44, schrieb Michael Tremer:
>>> Thanks.
>>>
>>> Are there plans to bring them into the stable tree?
>>>
>>> I don't think that there is much testing required and that we should put
>>> them right into the stable tree.
>>> If you think so as well, please drop a note to Arne.
>>>
>>> Michael
>>>
>>> On Sun, 2012-07-08 at 11:57 +0200, Erik K. wrote:
>>>> Hi Michael,
>>>> i have changed the URL for Tcpick and MTR but also of hostapd in the
>>>> english section. So the double dot in the end of the URL was missed .
>>>>
>>>>
>>>> The new URL´s are
>>>>
>>>>
>>>> German:
>>>> http://wiki.ipfire.org/de/addons/mtr/start
>>>> http://wiki.ipfire.org/de/addons/tcpick/start
>>>>
>>>>
>>>> English:
>>>> http://wiki.ipfire.org/en/addons/mtr/start
>>>> http://wiki.ipfire.org/en/addons/tcpick/start
>>>> http://wiki.ipfire.org/en/addons/wireless/start
>>>>
>>>>
>>>> The new addons aren´t in the stable tree. I have marked them as
>>>> (Testing) .
>>>>
>>>>
>>>> Erik
>>>>
>>>> Am 08.07.2012 um 10:53 schrieb Michael Tremer:
>>>>
>>>>> You shouldn't mix the URL types because you won't have the ability
>>>>> to
>>>>> switch languages very easily by clicking on the buttons in the right
>>>>> upper corner.
>>>>>
>>>>> Are these addons already in the stable tree?
>>>>>
>>>>> Michael
>>>>>
>>>>> On Sat, 2012-07-07 at 12:49 +0200, Erik K. wrote:
>>>>>>> Hi Daniel,
>>>>>>> thanks for response, try it with this link -->
>>>>>>> http://wiki.ipfire.org/de/addons/mtr/start . This is the
>>>>>>> original one from the wiki site.
>>>>>>>
>>>>>>> Erik
>>>>>>>
>>>>>>> Am 07.07.2012 um 08:39 schrieb whytea(a)ipfire.org:
>>>>>>>
>>>>>>>> Hi Erik,
>>>>>>>> The german mtr wiki dont work. Plz take a look.
>>>>>>>> - Daniel
>>>>>>>>
>>>>>>>> Gesendet mit meinem HTC
>>>>>>>>
>>>>>>>> ----- Reply message -----
>>>>>>>> Von: "Erik K." <ummeegge(a)ipfire.org>
>>>>>>>> An: "Mailingliste IPFire" <documentation(a)lists.ipfire.org>
>>>>>>>> Betreff: [Documentation] New documentation for new addons
>>>>>>>> Datum: Fr., Jul. 6, 2012 14:27
>>>>>>>>
>>>>>>>>
>>>>>>>> Hi all,
>>>>>>>> i have made two new documentations for "mtr" and "tcpick" in
>>>>>>>> german and english. Both addons are in the testing tree so i
>>>>>>>> have marked them equally in the appropriate section under
>>>>>>>> "Networktools (command-line)" .
>>>>>>>>
>>>>>>>> It might be nice if you can overview them and go for some
>>>>>>>> corrections if needed.
>>>>>>>>
>>>>>>>> The addresses are:
>>>>>>>>
>>>>>>>> in english section
>>>>>>>> http://wiki.ipfire.org/en/addons/mtr
>>>>>>>> http://wiki.ipfire.org/en/addons/tcpick
>>>>>>>>
>>>>>>>> and german:
>>>>>>>> http://wiki.ipfire.org/de/addons/mtr
>>>>>>>> http://wiki.ipfire.org/de/addons/tcpick
>>>>>>>>
>>>>>>>> Greetings to all
>>>>>>>>
>>>>>>>> Erik
>>>>>>>> _______________________________________________
>>>>>>>> Documentation mailing list
>>>>>>>> Documentation(a)lists.ipfire.org
>>>>>>>> http://lists.ipfire.org/mailman/listinfo/documentation
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Documentation mailing list
>>>>>> Documentation(a)lists.ipfire.org
>>>>>> http://lists.ipfire.org/mailman/listinfo/documentation
>>>>>
>>>>> _______________________________________________
>>>>> Documentation mailing list
>>>>> Documentation(a)lists.ipfire.org
>>>>> http://lists.ipfire.org/mailman/listinfo/documentation
>>>>>
>>>>
>>>> _______________________________________________
>>>> Documentation mailing list
>>>> Documentation(a)lists.ipfire.org
>>>> http://lists.ipfire.org/mailman/listinfo/documentation
>>>
>>> _______________________________________________
>>> Documentation mailing list
>>> Documentation(a)lists.ipfire.org
>>> http://lists.ipfire.org/mailman/listinfo/documentation
>>>
>>
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
>
--
__________________________________________
You need a firewall?
Easy to use? Powerful? Modular? For free?
www.ipfire.org
An Open Source Firewall Solution
next prev parent reply other threads:[~2012-07-09 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E0430EFB-7110-4B0E-BF5F-0FBB4D181E01@ipfire.org>
2012-07-09 8:44 ` Michael Tremer
2012-07-09 8:50 ` Daniel Weismüller
2012-07-09 8:55 ` Michael Tremer
2012-07-09 9:14 ` Daniel Weismüller
2012-07-09 9:47 ` Daniel Weismüller [this message]
[not found] <4C80304B-BBDB-49CE-A8F9-A9DB2E85E3A4@ipfire.org>
2012-07-07 10:49 ` Erik K.
2012-07-08 8:53 ` 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=4FFAA8CA.1040906@ipfire.org \
--to=whytea@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