public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Erik K." <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Aw: Re: GPG wiki
Date: Fri, 02 Aug 2013 19:46:38 +0200	[thread overview]
Message-ID: <ECCCE72E-E371-43A9-84B5-6991D7B7B4DE@ipfire.org> (raw)
In-Reply-To: <trinity-2d228474-01fc-4dc0-bce5-5cd3d6d0601e-1375457086070@3capp-gmx-bs30>

[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]

Hi Thomas,
think this was a good idea to extend this warnings.

Greetings

Erik

Am 02.08.2013 um 17:24 schrieb t.berthel(a)gmx.net:

> Hi,
> 
> next change for this topic.
> 
> I have comments leave a mobile device and the warning of loss of private keys. i take a hint: make a backup!
> http://wiki.ipfire.org/en/optimization/scripts/gpg/start
> 
>> Gesendet: Dienstag, 30. Juli 2013 um 10:40 Uhr
>> Von: "Erik K." <ummeegge(a)ipfire.org>
>> An: "Mailingliste IPFire" <documentation(a)lists.ipfire.org>
>> Betreff: Re: GPG wiki
>> 
>> Hi Thomas,
>> thanks for your feedback and your fixes. i did also some in the german section. 
>> One thing needs to changed in the next few days. A lot of links in this thread points to only in german written articles, may in the next few days there should also be a translation progress for them.
>> 
>> Greetings 
>> 
>> Erik
>> 
>> 
>> Am 29.07.2013 um 19:20 schrieb Thomas Berthel:
>> 
>>> Hi Erik,
>>> 
>>> very nice - thanks for the first translate! I have fixed little
>>> table-formating problems. It's a very long tobic and i hope so i have
>>> made no fault here that not seen yet in my native german tobic ;)
>>> 
>>> greetings, Thomas
>>> 
>>> Am 29.07.2013 18:20, schrieb Erik K.:
>>>> Hi all,
>>>> i want to introduce the first translation of the GPG wiki to english --> http://wiki.ipfire.org/en/optimization/scripts/gpg/start . This wiki is in the beginning of state (B) of the wiki workflow --> http://wiki.ipfire.org/projects/docs/workflow .
>>>> 
>>>> Please go for some checks on that.
>>>> 
>>>> Greetings
>>>> 
>>>> 
>>>> 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
>> 


  reply	other threads:[~2013-08-02 17:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 16:20 Erik K.
2013-07-29 17:20 ` Thomas Berthel
2013-07-30  8:40   ` Erik K.
2013-08-02 12:19     ` Michael Tremer
2013-08-02 12:53       ` Aw: " t.berthel
2013-08-02 15:24     ` t.berthel
2013-08-02 17:46       ` Erik K. [this message]
2013-08-06  7:54     ` SendEmail Wiki t.berthel
2013-08-06  8:40       ` Systemstate Script Wiki t.berthel
2013-08-06  9:13       ` SendEmail Wiki SCHUH Karl, SCHUH-TV
2013-08-06  9:32         ` Aw: " t.berthel
2013-08-06  9:32         ` Erik K.
2013-08-06 13:09         ` Documentation SCHUH Karl, SCHUH-TV
2013-08-06 15:21           ` Documentation 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=ECCCE72E-E371-43A9-84B5-6991D7B7B4DE@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