From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] fetch2/git: create bareclone option
Date: Fri, 24 Feb 2012 16:40:26 +0000 [thread overview]
Message-ID: <1330101626.5477.13.camel@ted> (raw)
In-Reply-To: <1330031322-22689-2-git-send-email-bruce.ashfield@windriver.com>
On Thu, 2012-02-23 at 16:08 -0500, Bruce Ashfield wrote:
> For similar reasons as the nocheckout option, packages that need
> enhanced control over the checkout and branch creation on a repository
> may want a complete mirror/bareclone created of the repository when
> performing the unpack.
>
> This is useful/required when a local respository is being used, but
> local tracking branches have not been created for all branches that
> a given recipe needs to manipulate. The standard git clone operations
> will create remote branches for the branches that are local to the
> source repository, but branches that are remote do not translate to
> the destination repository. Doing a mirror/bare clone of the source,
> makes all branches available to the repository.
>
> This is a particular use case, but the ability to do a bare clone
> creates great flexibility in recipe space, with no impact to recipes
> that don't need this functionality.
>
> To implement this, a new option 'bareclone' is craeted which creates
> a mirror copy of the repository and leaves it bare in the unpacking
> phase. A recipe that uses this option must both checkout and debare
> the repository itself.
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
> lib/bb/fetch2/git.py | 17 ++++++++++++++++-
> 1 files changed, 16 insertions(+), 1 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-02-24 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 21:08 fetch2/git: create bareclone option Bruce Ashfield
2012-02-23 21:08 ` [PATCH] " Bruce Ashfield
2012-02-24 16:40 ` Richard Purdie [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=1330101626.5477.13.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=bruce.ashfield@windriver.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