From: "Rifenbark, Scott M" <scott.m.rifenbark@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: couple observations on sync'ing up bitbake user manual and git.py fetcher
Date: Thu, 26 Jun 2014 05:31:12 -0700 [thread overview]
Message-ID: <53AC1290.8000302@linux.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1406191359260.15868@localhost>
On 6/19/2014 11:03 AM, Robert P. J. Day wrote:
> 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?
Correct.. I fixed this in the documentation.
>
> 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
>
prev parent reply other threads:[~2014-06-26 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 18:03 couple observations on sync'ing up bitbake user manual and git.py fetcher Robert P. J. Day
2014-06-26 12:31 ` Rifenbark, Scott M [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=53AC1290.8000302@linux.intel.com \
--to=scott.m.rifenbark@linux.intel.com \
--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 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.