From: Hollis Blanchard <hollis_blanchard@mentor.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: trouble using a local kernel repo
Date: Fri, 17 Feb 2012 08:45:24 -0800 [thread overview]
Message-ID: <4F3E8424.5070306@mentor.com> (raw)
In-Reply-To: <4F3D8AFD.6080307@windriver.com>
On 02/16/2012 03:02 PM, Bruce Ashfield wrote:
>
> 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.
One more workflow question: so to test my patch, I need to commit it to
my real git repo, then push to the bare git repo, then rebuild Poky.
When I find the inevitable problem, do I need to manually delete (git
reset --hard) the changeset from both repositories? Is there a better way?
Hollis Blanchard
Mentor Graphics, Embedded Systems Division
next prev parent reply other threads:[~2012-02-17 16:45 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
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 [this message]
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=4F3E8424.5070306@mentor.com \
--to=hollis_blanchard@mentor.com \
--cc=bruce.ashfield@windriver.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.