From: Thomas Fitzsimmons <fitzsim@cisco.com>
To: yocto@yoctoproject.org
Subject: Experimenting with kgit-scc
Date: Fri, 27 Apr 2012 16:18:48 -0400 [thread overview]
Message-ID: <m6pgwr51yllj.fsf@tfitzsim-lnx.cisco.com> (raw)
Hi,
Are there plans in the Yocto roadmap to make the meta/scripts/kgit tools
generally usable?
I like the organization of the Yocto kernel repository and for my
embedded project I'm considering using the Yocto build system along with
a Yocto-style kernel tree instead of maintaining my kernel patches as
recipe add-ons. The Yocto-style kernel repo could be either a local
clone of Yocto's kernel repo with extra machine-specific branches, or a
kernel.org tree locally post-processed by kgit-scc.
I experimented with meta/scripts/kgit-scc from linux-yocto-dev but the
kgit tools don't seem to be intended for general use yet (e.g. the -meta
files contain hard-coded home directory paths, and guilt-push complains
that guilt-init must be run first). The official Yocto documentation
says as much, but I was wondering if there are future plans to
generalize these tools.
Thanks,
Thomas
next reply other threads:[~2012-04-27 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 20:18 Thomas Fitzsimmons [this message]
2012-04-27 21:41 ` Experimenting with kgit-scc 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=m6pgwr51yllj.fsf@tfitzsim-lnx.cisco.com \
--to=fitzsim@cisco.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.