From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Aw: Please could someone review it
Date: Tue, 09 Jul 2013 16:59:35 +0200 [thread overview]
Message-ID: <1373381975.15464.91.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <1373018664.15464.49.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
I'm a bit disappointed, that this did not go as well as I expected.
Alex opened this new section about changes in the Core Updates and so
far it is empty.
If we want to maintain that, there needs to be someone responsible that
it is up to date. If it is running out of date, it is basically
worthless. Is anybody volunteering for this task? Is there a definition
of what has to be in there?
I am getting more and more complaints about the quality of the wiki and
documentation in general. Prepare for a discussion on that topic very
soon.
-Michael
On Fri, 2013-07-05 at 12:04 +0200, Michael Tremer wrote:
> The changes are backwards INcompatible. That means, that things MAY
> break.
>
> On Fri, 2013-07-05 at 11:42 +0200, Bernhard Bitsch wrote:
> > Is the change "backwards incompatible" or "abwärtskompatibel"?
> >
> > BTW: Das Verfassen von Doku in der Muttersprache vermeidet solche Probleme. ;)
>
> Please stop ranting about this topic. We discussed it several times and
> this problem does not prove your point.
>
> -Michael
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
prev parent reply other threads:[~2013-07-09 14:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 9:22 Daniel Weismüller
2013-07-05 9:42 ` Aw: " Bernhard Bitsch
2013-07-05 10:04 ` Michael Tremer
2013-07-09 14:59 ` Michael Tremer [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=1373381975.15464.91.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