From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Why IPFire does not run on all ARM hardware...
Date: Wed, 07 Aug 2013 20:22:07 +0200 [thread overview]
Message-ID: <1375899727.14644.16.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <assp.0931e90f83.52028DC3.3060203@dailydata.net>
[-- Attachment #1: Type: text/plain, Size: 1382 bytes --]
Hey Rod,
great to hear from you and thanks for the nice words about the article.
On Wed, 2013-08-07 at 13:11 -0500, R. W. Rodolico wrote:
> First, Michael, thank you for the excellent article. It was longer than
> normal, but well worth the read. I now understand why the ARM stuff is
> such a pain in the rear.
I hope that comes across. It was you who started all that ARM stuff and
I am still very happy that we worked on it and that we made such a huge
progress so far, but facing these problems, there will be an end of
these good days.
> Some of the articles are definitely transient (ie, new release, stuff
> like that), but articles like this are not. I was wondering if there is
> a need to place that article (and possibly others like it) in the
> documentation site. Under a special section?
May be it's a good idea to start a section and reference to the article
on the planet. But I thought it was a good idea writing this on the
planet, because the information on the planet ages a lot.
In a year, the situation about the ARM hardware could be completely
different and we usually are not able to keep the wiki as up to date as
it should be.
Hope the language was okay :)
-Michael
>
> Rod
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
prev parent reply other threads:[~2013-08-07 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 18:11 R. W. Rodolico
2013-08-07 18:22 ` 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=1375899727.14644.16.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