From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: BitBake developer list <bitbake-devel@lists.openembedded.org>
Subject: couple observations on sync'ing up bitbake user manual and git.py fetcher
Date: Thu, 19 Jun 2014 14:03:12 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.11.1406191359260.15868@localhost> (raw)
short observations someone higher up the food chain is welcome to
resolve:
in this section:
http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#git-fetcher
explanation of "tag" parameter refers to "revision" parameter, should
be just "rev" parameter, no?
and in git.py fetcher file itself, in the early self-contained
documemntation, there is no mention of any of the "rev", "subpath" or
"destsuffix" parameters.
that's it for now.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2014-06-19 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 18:03 Robert P. J. Day [this message]
2014-06-26 12:31 ` couple observations on sync'ing up bitbake user manual and git.py fetcher 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.1406191359260.15868@localhost \
--to=rpjday@crashcourse.ca \
--cc=bitbake-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox