From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Ulf Samuelsson <openembedded@emagii.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Support for R/W git in bitbake
Date: Wed, 18 Apr 2012 00:07:17 +0100 [thread overview]
Message-ID: <2900608.HO3vnnHahd@helios> (raw)
In-Reply-To: <4F8DF031.60109@emagii.com>
On Wednesday 18 April 2012 00:35:29 Ulf Samuelsson wrote:
> Today bitbake supports read only git access in recipes.
> For various reasons, I would like to be able to do recipes
> which would check out in a read/write mode.
Could you elaborate on "various reasons"?
Would the new externalsrc bbclass be useful in your case?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-04-17 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 22:35 RFC: Support for R/W git in bitbake Ulf Samuelsson
2012-04-17 23:07 ` Paul Eggleton [this message]
2012-04-18 1:34 ` Ulf Samuelsson
2012-04-18 6:24 ` Antonio Ospite
2012-04-19 7:25 ` Anders Darander
2012-04-18 7:28 ` Paul Eggleton
2012-04-18 8:12 ` Ulf Samuelsson
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=2900608.HO3vnnHahd@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded@emagii.com \
/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