All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Brian Hutchinson <b.hutchman@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Does Edison work with Beagleboard & linux-yocto-3.0 kernel?
Date: Thu, 12 Jan 2012 11:24:27 -0500	[thread overview]
Message-ID: <4F0F093B.7000408@windriver.com> (raw)
In-Reply-To: <CAFZh4h8Z3GW8mrsgpHVQCQgHpg1CpmwmP=xMXcitA=h4A1L52A@mail.gmail.com>

On 12-01-12 11:20 AM, Brian Hutchinson wrote:
> On Thu, Jan 12, 2012 at 11:00 AM, Bruce Ashfield
> <bruce.ashfield@windriver.com>  wrote:
>> The bitbake AUTOREV code should take care of updating the clone
>> of your local repo in downloads/git2. I take it that this isn't
>> happening ?
>
> ... haven't tried ... was just sticking to the example in the
> documentation which says to push changes and do a cleanall.  The spin

Good point. I hadn't noticed that it was in there. Worth trying
without it, and raising a bug if it isn't required. It's
bitbake internals rather than kernel at play here, so I'm far
from authoritative about what should or shouldn't work.

> time on my dev machine wasn't too bad but long enough to get old quick
> if I had to do it often.

Agreed!

>
>> It should be (largely) as simple as that. We could create something
>> simple and throw it in with the meta-kernel-dev layer if there's any
>> interest in adding it.
>
> Just wanting to know what the "best practice" is as I have lots of
> platforms to support.

I prefer to work this way, since managing patches in a source git
repository is much easier for me. If you only have a few patches,
then they can just be pushed on top and added to the SRC_URI, but
you'd be doing more development under tmp/work/ in that case .. and
I'm paranoid about losing things :)

Cheers,

Bruce

>
> Regards,
>
> Brian



  reply	other threads:[~2012-01-12 16:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 14:41 Does Edison work with Beagleboard & linux-yocto-3.0 kernel? Brian Hutchinson
2012-01-11 14:57 ` Bruce Ashfield
2012-01-11 15:20   ` Brian Hutchinson
2012-01-11 15:24     ` Jack Mitchell
2012-01-11 15:31       ` Bruce Ashfield
2012-01-11 15:29     ` Bruce Ashfield
2012-01-11 16:29       ` Brian Hutchinson
2012-01-11 20:35         ` Brian Hutchinson
2012-01-11 20:46           ` Bruce Ashfield
2012-01-11 20:50             ` Brian Hutchinson
2012-01-11 20:47 ` Joshua Lock
2012-01-11 20:57   ` Brian Hutchinson
2012-01-12 15:21     ` Brian Hutchinson
2012-01-12 15:56       ` Jack Mitchell
2012-01-12 16:29         ` Brian Hutchinson
2012-01-12 16:00       ` Bruce Ashfield
2012-01-12 16:20         ` Brian Hutchinson
2012-01-12 16:24           ` Bruce Ashfield [this message]
2012-01-12 16:48             ` Brian Hutchinson
2012-01-12 18:28               ` Bruce Ashfield
2012-01-15  8:47     ` Koen Kooi
2012-01-15 17:35       ` Brian Hutchinson
2012-01-23  3:33 ` Brian Hutchinson
2012-01-23  3:55   ` Bruce Ashfield
2012-01-23 19:40     ` Brian Hutchinson

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=4F0F093B.7000408@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=b.hutchman@gmail.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.