All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: Yocto discussion list <yocto@yoctoproject.org>
Subject: [PATCH] Yocto Project Dev Manual - bad reference in dev-manual-newbie.xml
Date: Sat, 01 Dec 2012 10:15:19 -0500	[thread overview]
Message-ID: <50BA1F07.3030802@mindchasers.com> (raw)

I updated a note that points the reader to the maintainers list.  The 
note in the master branch pointed the reader to a nonexistent (old) file.

Signed-off-by: Robert Cochran<yocto@mindchasers.com>

---
  documentation/dev-manual/dev-manual-newbie.xml |    4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/documentation/dev-manual/dev-manual-newbie.xml 
b/documentation/dev-manual/dev-manual-newbie.xml
index bb01131..8b078e1 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -742,8 +742,8 @@
          The maintainer is responsible for allowing changes in from 
other developers and for
          organizing the underlying branch structure to reflect release 
strategies and so forth.
          <note>You can see who is the maintainer for Yocto Project 
files by examining the
-        <filename>distro_tracking_fields.inc</filename> file in the 
Yocto Project
-        <filename>meta/conf/distro/include</filename> directory.</note>
+        <filename>maintainers.inc</filename> file in the Yocto Project
+        <filename>meta-yocto/conf/distro/include</filename> 
directory.</note>
      </para>

      <para>
-- 
1.7.9.5


             reply	other threads:[~2012-12-01 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-01 15:15 Bob Cochran [this message]
2012-12-07 23:08 ` [PATCH] Yocto Project Dev Manual - bad reference in dev-manual-newbie.xml 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=50BA1F07.3030802@mindchasers.com \
    --to=yocto@mindchasers.com \
    --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.