Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: "Yong, Jonathan" <jonathan.yong@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 1/1] bitbake-user-manual: document git usehead argument
Date: Tue,  4 Dec 2018 05:37:53 +0000	[thread overview]
Message-ID: <20181204053753.44975-2-jonathan.yong@intel.com> (raw)
In-Reply-To: <20181204053753.44975-1-jonathan.yong@intel.com>

usehead functionality is already present, document it.

Signed-off-by: Yong, Jonathan <jonathan.yong@intel.com>
---
 doc/bitbake-user-manual/bitbake-user-manual-fetching.xml | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml b/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml
index 29ae486a7..341ce9998 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml
+++ b/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml
@@ -588,6 +588,11 @@
                         The name of the path in which to place the checkout.
                         By default, the path is <filename>git/</filename>.
                         </para></listitem>
+                   <listitem><para><emphasis>"usehead":</emphasis>
+                        For local git:// urls to use the current branch HEAD
+                        as the revision for use with AUTOREV. Implies nobranch.
+                        Will only work when protocol is "file".
+                        </para></listitem>
                 </itemizedlist>
                 Here are some example URLs:
                 <literallayout class='monospaced'>
-- 
2.19.2



  reply	other threads:[~2018-12-04  5:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04  5:37 [PATCH 0/1] document git usehead argument Yong, Jonathan
2018-12-04  5:37 ` Yong, Jonathan [this message]
2018-12-07  0:36 ` Yong, Jonathan

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=20181204053753.44975-2-jonathan.yong@intel.com \
    --to=jonathan.yong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox