From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@openembedded.org
Subject: Re: where to send notes about broken links at http://openembedded.org/?
Date: Wed, 4 Nov 2009 02:20:15 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911040219220.2006@localhost> (raw)
In-Reply-To: <200911040220.12642.holger+oe@freyther.de>
On Wed, 4 Nov 2009, Holger Hans Peter Freyther wrote:
> On Tuesday 03 November 2009 17:15:39 Robert P. J. Day wrote:
> > i've decided to go thru the OE documentation thoroughly once and
> > for all, so i'm starting at http://openembedded.org/ to pull
> > together everything i need to truly understand how it works, and
> > i've already noticed a few glitches. some broken links at the top
> > of that page: both the OpenEmbedded and OpenZaurus links seem to
> > be borked, at least as far as my ISP rogers is concerned. oh, and
> > the G(PE)^2 link as well.
> >
> > is this the right place to report this? or is there an
> > individual webmaster i should harass with this sort of stuff?
>
> Report them, or if they are in the wiki please fix them right away.
ok, i just created a wiki account for myself, but i'm guessing some
of the stuff i find won't be wiki content so be prepared for the
occasional comment here as well.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
prev parent reply other threads:[~2009-11-04 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 16:15 where to send notes about broken links at http://openembedded.org/? Robert P. J. Day
2009-11-04 1:20 ` Holger Hans Peter Freyther
2009-11-04 7:20 ` Robert P. J. Day [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=alpine.LFD.2.00.0911040219220.2006@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.