From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] Cryptodev support in Core Update 58
Date: Tue, 08 May 2012 12:52:27 +0200 [thread overview]
Message-ID: <1336474347.15371.95.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <4FA8D395.1020203@directbox.de>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
Thank you very much, Daen. That was fast...
Michael
On Tue, 2012-05-08 at 10:04 +0200, dh(a)directbox.de wrote:
> Hi,
>
> die Übersetzung steht, sollte aber noch mal von jemandem, der mit den
> technischen Hintergründen vertraut ist, gegengecheckt werden. Ich habe
> das einfach so übersetzt, wie es für mich Sinn gemacht hat.
>
> Gruß
> daen
>
> Am 07.05.2012 22:11, schrieb Michael Tremer:
> > Hello,
> >
> > Core Update 58 is in its final state and we are now checking for the
> > documentation of the new feature: cryptodev.
> >
> > I created a short wiki site that contains some technical stuff and a
> > notice for all the Geode users out there.
> >
> > I would like the Documentation team to create a German translation and
> > check on the English version (spelling and maybe make it a bit more
> > user-friendly).
> >
> > http://wiki.ipfire.org/en/optimization/cryptodev
> >
> > This is currently blocking the release of Core Update 58. Therefore I
> > would be glad if you could get this done quickly.
> >
> > Michael
> >
> > _______________________________________________
> > Documentation mailing list
> > Documentation(a)lists.ipfire.org
> > http://lists.ipfire.org/mailman/listinfo/documentation
>
>
next parent reply other threads:[~2012-05-08 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FA8D395.1020203@directbox.de>
2012-05-08 10:52 ` Michael Tremer [this message]
[not found] <CAO6L5t_zZ1=d7GMMvnEwUvDpNh_O7Au6bE73g+KPkgJeujwNkw@mail.gmail.com>
2012-05-17 16:32 ` Michael Tremer
2012-05-07 20:11 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=1336474347.15371.95.camel@rice-oxley.tremer.info \
--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