From: "R. W. Rodolico" <rodo@dailydata.net>
To: documentation@lists.ipfire.org
Subject: Why IPFire does not run on all ARM hardware...
Date: Wed, 07 Aug 2013 13:11:15 -0500 [thread overview]
Message-ID: <assp.0931e90f83.52028DC3.3060203@dailydata.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
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.
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?
Rod
--
R. W. "Rod" Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
http://www.dailydata.net
214.827.2170
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: rodo.vcf --]
[-- Type: text/x-vcard, Size: 233 bytes --]
begin:vcard
fn:R. W. Rodolico
n:Rodolico;R. W.
org:Daily Data, Inc.
adr:;;POB 140465;Dallas;TX;75214-0465;US
email;internet:rodo@dailydata.net
title:President
tel;work:214.827.2170
url:http://www.dailydata.net
version:2.1
end:vcard
next reply other threads:[~2013-08-07 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 18:11 R. W. Rodolico [this message]
2013-08-07 18:22 ` 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=assp.0931e90f83.52028DC3.3060203@dailydata.net \
--to=rodo@dailydata.net \
--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