public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: "SCHUH Karl, SCHUH-TV" <k.schuh@schuh-tv.at>
To: documentation@lists.ipfire.org
Subject: Re: DNS Forwarding + Wireless Client + Tor [week two]
Date: Mon, 12 Aug 2013 19:16:09 +0200	[thread overview]
Message-ID: <10237721.2870.1376327769852.JavaMail.root@jupiter2> (raw)
In-Reply-To: <1376322955.18941.22.camel@rice-oxley.tremer.info>

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

Hi Michael,
maybe it would be more important if start the translation process. If someone wanted to start a translation, he could look up the english version, if it were stable or if it was worked upon. But there can be other rules to avoid a translation of a page, which is to be changed (as it happened to me with the NDS-forward-page). :-)

Best regards,
Karl 

----- Ursprüngliche Mail -----
> Well, I didn't feel that it made much sense, because if someone is
> actually working on a page, the wiki software will lock it, so that
> there won't be any conflicts.
> Otherwise, I didn't think that the team is big enough to divide it
> into
> several groups who each work on a page.
> 
> Why do you think do we need this?
> 
> -Michael

-- 
Ing. Karl SCHUH 

Hauptstraße 23a 
A-7434 Bernstein 
+43(664)38 06 107 

  reply	other threads:[~2013-08-12 17:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-10 13:13 Michael Tremer
2013-08-10 16:05 ` SCHUH Karl, SCHUH-TV
2013-08-12 15:55   ` Michael Tremer
2013-08-12 17:16     ` SCHUH Karl, SCHUH-TV [this message]
2013-08-12 17:28       ` Michael Tremer
2013-08-17 10:41         ` Michael Tremer
     [not found] <CAKTTqHOX5OMVSeLVwvPKAQ1sR=9xgWDKA+VJNOZrnT+nSNWTGQ@mail.gmail.com>
2013-08-17 11:00 ` Michael Tremer
2013-08-19  6:46   ` R. W. Rodolico
2013-08-19 20:13     ` Michael Tremer
2013-08-21  0:53       ` R. W. Rodolico
2013-08-21 18:34         ` 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=10237721.2870.1376327769852.JavaMail.root@jupiter2 \
    --to=k.schuh@schuh-tv.at \
    --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