On 01/31/2012 09:28 PM, Wang, Shane wrote: Thanks for the example Shane, good idea.
> Here is my example of the steps after you source the environment and "git > push" to poky-contrib. > > Run: create-pull-request -b shane/typo -u origin-pc3 -r > 238a47d800446996f5cb9929f33aaaffe618f7b6 -s "fix the typos for package report > system" -r accepts any git revision, hash, branch, tag, etc. > Edit: the pull-3635/0000-XXXX file > Run: send-pull-request -p pull-3635 -t > openembedded-core@lists.openembedded.org I use a .gitaliases.mutt file so I don't have to type openembedded-core quite so often :-) $ grep oe-core ~/.gitaliases.mutt alias oe-core openembedded-core@lists.openembedded.org Also have a look at the -c and -a options to pull names from the various patch signatures. -- Darren > -- > Shane > > Steve Sakoman wrote on 2012-02-01: > >> On Tue, Jan 31, 2012 at 11:28 AM, Darren Hart <dvh...@linux.intel.com> >> wrote: >>> Did you send this using the send-pull-request script? I assume not as >>> this was to oe-core and not yocto, but if you did, I want to know as it >>> should protect against -ENOCOFFEEYET errors such as these. >> >> No, I used git send-email. >> >> I'm not familiar with the send-pull-request script. I wouldn't have >> guessed from the name that it is a mailing list patch submission >> script. Is it hardwired to the yocto list? >> >>> For whatever it's worth, I use this script for all my projects now to >>> help avoid situations like this which I have fallen into more times than >>> I care to admit :-) >> >> Indeed, I very often catch myself forgetting to add the subject to the >> cover letter! I'll have to investigate using the send-pull-request >> script. >> >> Steve >> >>> On 01/30/2012 09:17 AM, Steve Sakoman wrote: >>>> Sigh, my morning for screw-ups. Time for another cup of coffee . . . >>>> >>>> The subject should be: 'zypper: support signed repositories' rather >>>> than '***SUBJECT HERE***' :-) >>>> >>>> Steve >>>> >>>> On Mon, Jan 30, 2012 at 9:14 AM, Steve Sakoman <st...@sakoman.com> >> wrote: >>>>> The current zypper implementation does not work with signed >>>>> repositories. This patch series adds recipes for the required >>>>> packages as well as the necessary runtime dependencies to zypper. >>>>> >>>>> Tested on Gumstix Overo (OMAP3) with meta-openembedded layer enabled >>>>> and a systemd based console image. >>>>> >>>>> Version 3 incorporates feedback from Koen Kooi and Saul Wold >>>>> - adds runtime dependencies to existing RDEPENDS_${PN} >>>>> - removes duplicate recipe for libassuan >>>>> - moves recipes for gnupg and libksba to recipes-support >>>>> >>>>> Steve Sakoman (3): >>>>> libksba: add recipe for 1.2.0 >>>>> gnupg: add recipe for 2.0.18 >>>>> zypper: add missing runtime dependences on gzip and gnupg >>>>> >>>>> meta/recipes-extended/zypper/zypper_git.bb | 4 ++-- >>>>> meta/recipes-support/gnupg/gnupg_2.0.18.bb | 24 >>>>> ++++++++++++++++++++++++ >>>>> meta/recipes-support/libksba/libksba_1.2.0.bb | 10 ++++++++++ 3 >>>>> files changed, 36 insertions(+), 2 deletions(-) create mode 100644 >>>>> meta/recipes-support/gnupg/gnupg_2.0.18.bb create mode 100644 >>>>> meta/recipes-support/libksba/libksba_1.2.0.bb >>>>> >>>> >>>> _______________________________________________ >>>> Openembedded-core mailing list >>>> Openembedded-core@lists.openembedded.org >>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core >>> >>> -- >>> Darren Hart >>> Intel Open Source Technology Center >>> Yocto Project - Linux Kernel >> >> _______________________________________________ Openembedded-core >> mailing list Openembedded-core@lists.openembedded.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core > > -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core