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 13:28:14 -0500	[thread overview]
Message-ID: <4F0F263E.2070201@windriver.com> (raw)
In-Reply-To: <CAFZh4h-DRM-4zrBdiBwPH7T0bo+Ba5NGgPi5ppek33XmWtfJsw@mail.gmail.com>

On 12-01-12 11:48 AM, Brian Hutchinson wrote:
> On Thu, Jan 12, 2012 at 11:24 AM, Bruce Ashfield
> <bruce.ashfield@windriver.com>  wrote:
>> 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 :)
>
> I know it probably isn't the best way (did it mostly because I was in
> a hurry and never took the time to think about the "right" way to do
> it) but I've made changes to the kernel&  u-boot before in the tmp
> directories (with Angstrom and Arago) and build images manually (make
> uImage etc.) and that was OK for quick/dirty things but I've gotten
> burned before by forgetting my changes and doing a bitbake build and
> wiping out my changes.   I like the method of pointing yocto to local
> git repos and think that is better for long term development as it
> will contain history and would be easy to determine what changed etc.
> I'd like to do something similar with u-boot and thought you guys had
> worked out a defacto standard way but in looking through all the docs
> it doesn't look that way.

Ah yes. Nothing in particular. I was a non-oe import to yocto, so a
lot of what I've done is from being bitten in the past and making sure
that it didn't happen to me in a new environment.

Of course, I'm all for general solutions and getting feedback as well!

Cheers,

Bruce

>
> Regards,
>
> Brian



  reply	other threads:[~2012-01-12 18:28 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
2012-01-12 16:48             ` Brian Hutchinson
2012-01-12 18:28               ` Bruce Ashfield [this message]
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=4F0F263E.2070201@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.