From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Hollis Blanchard <hollis_blanchard@mentor.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: trouble using a local kernel repo
Date: Thu, 16 Feb 2012 18:02:21 -0500 [thread overview]
Message-ID: <4F3D8AFD.6080307@windriver.com> (raw)
In-Reply-To: <4F3D883C.8070709@mentor.com>
On 12-02-16 05:50 PM, Hollis Blanchard wrote:
> On 02/16/2012 02:11 PM, Bruce Ashfield wrote:
>> On 12-02-16 03:16 PM, Hollis Blanchard wrote:
>>> I'm trying to figure out how to use a cloned/modified copy of the
>>> linux-yocto-3.0 git repository. Here's what I did:
>>>
>>> * cloned linux-yocto-3.0.git and committed to the meta branch
>>> * specified my new repo:
>>
>> Very strange. Is this from the yocto master branch ?
>
> I ran this:
>
> git clone git://git.yoctoproject.org/linux-yocto-3.0
> git checkout -t origin/meta -b meta
> vim
> git commit
>
>
> [snip]
>> That being said. If you go into your src tree. Do you see the meta and
>> board branch ? Are they local branches ? Is your SRC_URI pointing at a
>> bare clone, and not a non-bare one ?
>
> As you can tell from my clone command above, it is a non-bare clone
> (though I have no idea what that actually means). I have lots of
> branches, but aside from master only my new "meta" branch is local:
That's the problem. I have a patch that detects this and abort is a non
bare upstream is used. I just need to send them .. which I'll do when
I get back to my desk next week.
There are two reason for this bare clone requirement:
- technical: this scales to several hundred branches. cloning, and
iterating
remote branches to create local tracking branches is noisy and
time consuming. So there's a trick that has been in use for years
that you can clone a bare upstream, and mass convert the branches
to local in a single operation.
- social: you want to do your development in a different tree from the
one that is being cloned and used. That way the tree is clean, and you
are building what you expect.
This was supposed to be added to the new documentation (in the smaller,
lightened versions) .. but I don't think that is out yet.
Cheers,
Bruce
>
> -bash-3.2$ git branch -a
> master
> * meta
> origin/HEAD
> origin/master
> origin/meta
> origin/yocto/base
> origin/yocto/eg20t
> origin/yocto/emgd
> origin/yocto/emgd-1.10
> origin/yocto/gma500
> origin/yocto/standard/arm-versatile-926ejs
> origin/yocto/standard/base
> origin/yocto/standard/beagleboard
> [...]
>
>
> Hollis Blanchard
> Mentor Graphics, Embedded Systems Division
>
>
next prev parent reply other threads:[~2012-02-16 23:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 20:16 trouble using a local kernel repo Hollis Blanchard
2012-02-16 21:22 ` McClintock Matthew-B29882
2012-02-16 21:33 ` Hollis Blanchard
2012-02-16 21:43 ` McClintock Matthew-B29882
2012-02-16 22:06 ` Hollis Blanchard
2012-02-16 22:14 ` Bruce Ashfield
2012-02-16 22:11 ` Bruce Ashfield
2012-02-16 22:50 ` Hollis Blanchard
2012-02-16 23:02 ` Bruce Ashfield [this message]
2012-02-16 23:18 ` Hollis Blanchard
2012-02-16 23:25 ` Bruce Ashfield
2012-02-16 23:52 ` Hollis Blanchard
2012-02-17 0:13 ` Bruce Ashfield
2012-02-17 16:45 ` Hollis Blanchard
2012-02-17 19:56 ` Bruce Ashfield
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=4F3D8AFD.6080307@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=hollis_blanchard@mentor.com \
--cc=yocto@yoctoproject.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.