All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Ferland <ferlandm@sonatest.com>
To: yocto@yoctoproject.org
Subject: linux-yocto and private topic branches
Date: Fri, 17 Aug 2012 16:21:28 -0400	[thread overview]
Message-ID: <871uj51d87.fsf@sonatest.com> (raw)

Hi,

I'm maintaining a BSP based on crownbay and I would like to change my
current kernel recipe from a custom one to linux-yocto_3.2.bb.

Reading the kernel-yocto.bbclass, I see that it is possible to provide a
list of patches and configuration fragments but also (not sure about
that) to provide an "external branch".

Since we maintain several private topic branches in-house this would be
the perfect solution. I could "inherit" from crownbay (available on
linux-yocto) and just merge my topic branches to produce the final
kernel source tree.

My question:
Is this currently possible? If so, are there any examples available?
Can these changes be kept in "recipe-space"?

If not possible, am I stuck with managing patches?

Regards,

Marc


             reply	other threads:[~2012-08-17 20:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 20:21 Marc Ferland [this message]
2012-08-17 20:35 ` linux-yocto and private topic branches Bruce Ashfield
2012-08-17 21:33   ` Marc Ferland
2012-08-20  4:30     ` 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=871uj51d87.fsf@sonatest.com \
    --to=ferlandm@sonatest.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.