| Age | Commit message (Collapse) | Author | Files |
|---|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
exists there
[BUGID #533]
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Joshua Lock <josh@linux.intel.com>
|
|
send-pull-request facilitates sending pull requests generated by
create-pull-request. The primary role of this script is to harvest email
addresses from the patches and send them out. A working installation of sendmail
(exim, postfix, msmtp, etc.) is required to use this script.
You can explicitly specify To addresses with the -t option. As this can be
tedious, the -a option will scan all the patches for To, CC, and *-by lines and
the collected addresses to the To and CC headers for each patch.
This script uses an identical recipients list for every patch, including the
cover letter. This is by design. Existing tools will auto-generate the CC header
for individual patches, but since they don't apply it to the other patches, the
recipients can lack the necessary context to provide a meaningful review. This
is especially true of the cover letter.
The pull directory generated by the create-pull-request script is specified
using the -p option.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Nitin A Kamble <nitin.a.kamble@intel.com>
CC: Richard Purdie <rpurdie@linux.intel.com>
CC: Saul Wold <saul.wold@intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The previous create-pull-request only generated a cover letter. When used to
send to the list, it did not include the patches, which made it difficult
to perform peer review. A pull request without patches is typically only sent
by a maintainer. As we are not all maintainers, we need a means to easily
submit patches for review.
As we are accustomed to making pull requests, this script retains a
git-pull-style cover letter, while sending the relevant patches as responses
to the pull. This will provide the necessary context for peer review, and still
allow people to collapse threads and see no more mail than they were previously.
This version retains the relative_to, commit_id, and contrib_branch arguments
from the original, along with their default values. It adds several more,
resulting in a highly flexible tool.
The script creates a pull directory (pull-$$ by default, configurable via the -o
option) and populates it with a git-format-patch generated patch series and
cover letter. The cover letter is modified to include the git and http pull URLs
and branch name, as well as a basic signature from the author pulled from git's
user.name and user.email config. git-format-patch provides the shortlog and
diffstat of the series.
Breaking a bit from the original, this script maintains the [PATCH] subject
prefix in the cover letter (as opposed to [GIT PULL]. This is better suited to
the majority of developers (who are not maintainers). This prefix is
configurable with the -p option, allowing you to create an [RFC PATCH]
prefix, for example.
By default, the generated cover letter with contain "*** SUBJECT HERE ***" and
"*** BLURB HERE ***" tokens which you should replace with something
appropriate prior to sending the messages.
When developing multiple versions of a patch series, it can save time to
maintain a message.txt file, rather than having to retype the message body of
the cover letter every time. The -m option allows you to specify a message file
and replace the "*** BLURB HERE ***" token of the cover letter with the contents
of the message file.
Finally, the -s option will replace the "*** SUBJECT HERE ***" token in the cover
letter with the specified subject.
The generated patches are suitable for sending via sendmail.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Nitin A Kamble <nitin.a.kamble@intel.com>
CC: Richard Purdie <rpurdie@linux.intel.com>
CC: Saul Wold <saul.wold@intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
The patches to follow completely rewrite the existing create-pull-request.
Rather than have an initial diff of the two files (which are not at all
similar) remove the original, and then create the new one.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Nitin A Kamble <nitin.a.kamble@intel.com>
CC: Richard Purdie <rpurdie@linux.intel.com>
CC: Saul Wold <saul.wold@intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Move /usr/lib/libtcl8.5.so into tcl-lib package.
Signed-off-by: Jingdong Lu <jingdong.lu@windriver.com>
|
|
The custom uImage produced by the kernel classes by default
does not universally boot and working with existing uboot
configurations and setups.
This changes the preference to the uImage constructed by
the kbuild processes and falls back to the other techniques
if uImage is requested by the kernel does not produce one.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
It is useful to override revision checking from a layer or other
recipe. In order to show the global nature of the variable rename
it KERNEL_REVISION_CHECKING and make it a weak assignment.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Fixes [BUGID: #394]
qemumips: Added wacom tablet support to mti_malta32_be bsp config
Signed-off-by: J. Aaron Gamble <john.gamble@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Fixes [BUGID #394]
Now that the qemu/mti mips kernel branches have been fixed
for wacom USB interaction, we can re-nable the standard set
of qemu UI options for qemumips.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Fixes [BUGID #394]
patch added from: https://launchpad.net/ubuntu/+source/tslib/1.0-7
Enables wacom tablet/touchscreen support on qemumips
Signed-off-by: J. Aaron Gamble <john.gamble@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Fixes [BUGID #394]
Signed-off-by: J. Aaron Gamble <john.gamble@windriver.com>
|
|
OpenSuSE 11.3 uses GNU patch 2.6.1.81-5b68 which breaks quilt's
configure test for patch version.
Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com>
|
|
Add en-us and POSIX to default locale generation
Signed-off-by: Saul Wold <Saul.Wold@intel.com>
|
|
Signed-off-by: Saul Wold <Saul.Wold@intel.com>
|
|
${sysconfdir} should be added into FILES_${PN}.
Fixes [BUGID #511]
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
|
|
Signed-off-by: Saul Wold <Saul.Wold@intel.com>
|
|
Fixes [BUGID #495]
Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
|
|
resolves security bug CVE-2010-0405
Signed-off-by: Qing He <qing.he@intel.com>
|
|
Add a test case for error log check with command dmesg in target. The
case introduces a new folder in target, "/opt/test", which holds test
scripts running in target.
Signed-off-by Jiajun Xu <jiajun.xu@intel.com>
|
|
Signed-off-by: Saul Wold <Saul.Wold@intel.com>
|
|
Signed-off-by: Saul Wold <Saul.Wold@intel.com>
|
|
duplicate providers warning
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Joshua Lock <josh@linux.intel.com>
|
|
Make 3.82, as shipped with Fedora 14, fixes some holes in the parser which in
turn breaks behaviour of some Makefiles. Most notably eglibc's.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
|
|
package sstate requires a lock under sysroots/, which however may not be
created when sstate_setscene functions are executed and then causes failures.
here we make sure 'sysroots' created before do_package_setscene is executed.
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
|
|
Without doing this I can't reuse prebuilts generated from one directory in another
build directory which is really not comfortable for developers. Due to difference
on PWD variable, base hash becomes different for every sstate package.
So here PWD is added to the hase base whitelist, which makes most prebuilts reusable
now in a different build directory. However there still remains one issue about
do_populate_sysroot sstate package. Absolute path is encoded in this task which
then blocks reuse on them. Perhaps we need some redesign for do_populate_sysroot into
two stages, with all absolute path related operations moved to the 2nd stage. This
way then the 1st stage can be reused.
Partially fix [BUGID #522]
Signed-off-by Kevin Tian <kevin.tian@intel.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
many english corrections performed.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I completed the editing pass of this chapter by doing sections 3.3.3 on.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I created a new sub folder to hold the BSP Guide by itself so there are
three folders now for each of the Yocto manuals: BSP Guide, quick start
and poky ref manual. The new folder for the BSP guide is 'bsp-guide'.
It contains the bsp.xml file, its own Makefile, a bsp-guide.xml file,
and its own 'Figures' directory. The 'bsp-guide.xml' file that was
in the poky reference folder was deleted.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I completed general edits to the second chapter of the poky reference
manual. These edits went from section 2.4.5 through the end of the
chapter. They consist of text rewrites for more active voice and follow
general technical writing principles.
I completed the same types of edits in the third chapter of the manual
from the beginning through section 3.3.2.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Extensive language and consistency edits being applied to the manual.
During the 0.9 push I did not have time to make a pass through the
document.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Changed "source poky-4.0/poky-init-build-env poky-4.0-build"
to be "source poky-laverne-4.0/poky-init-build-env poky-4.0-build"
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
There was a grammatical error in the title and redundancy in the
first sentence of this section. Cleaned up the title and wording.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I did a complete edit pass through this chapter. The manual has
not been fully edited from its original state. One critical technical
correction was corrected where the green-3.3 release was referenced.
I changed this to laverne 4.0.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
I changed the figure that goes along with building an image based on
Kevin's input. Also, removed several URLs that had 'yoctolinux' in them
along with a 'tar' command example with the same string. LF does
not want these in there.
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
|
|
Signed-off-by: Koen Kooi <k-kooi@ti.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
point to incorrect places
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
components in builds from scratch using sstate
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
standalone python tarball
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
