All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: current dev manual possibly links to out-of-date wiki page(s)
Date: Mon, 5 Jan 2015 07:22:47 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1501050718160.7372@localhost> (raw)


  section 4.1.1, dev manual:

"Finally, there is a wiki page write up of the example also located
here that you might find helpful."
^^^^

  that link takes one here:

https://wiki.yoctoproject.org/wiki/Transcript:_creating_one_generic_Atom_BSP_from_another

and while it's not fatal to link to older wiki material, it does read
as odd to link to a wiki page that, in its very opening, admits that
its content might not be current.

  in addition, *that* wiki page quickly links here:

https://wiki.yoctoproject.org/wiki/Yocto_BSP_Tools_Documentation

which again admits that its content is to be obsoleted by the official
BSP Guide.

  in any event, i'll leave it to someone else to decide on the
efficacy of having official docs link to potentially transient wiki
pages.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


             reply	other threads:[~2015-01-05 12:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 12:22 Robert P. J. Day [this message]
2015-01-06 15:15 ` current dev manual possibly links to out-of-date wiki page(s) Rifenbark, Scott M

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.11.1501050718160.7372@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=yocto@yoctoproject.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.