From: Darren Hart <dvhart@linux.intel.com>
To: "Wang, Shane" <shane.wang@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3 0/3] *** SUBJECT HERE ***
Date: Tue, 31 Jan 2012 22:57:07 -0800 [thread overview]
Message-ID: <4F28E243.4040108@linux.intel.com> (raw)
In-Reply-To: <3AB6CE7F274E534CAFD089D127A8A1FC0FCE97B9@SHSMSX102.ccr.corp.intel.com>
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 <dvhart@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 <steve@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
next prev parent reply other threads:[~2012-02-01 7:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 17:14 [PATCH v3 0/3] *** SUBJECT HERE *** Steve Sakoman
2012-01-30 17:14 ` [PATCH v3 1/3] libksba: add recipe for 1.2.0 Steve Sakoman
2012-01-30 17:14 ` [PATCH v3 2/3] gnupg: add recipe for 2.0.18 Steve Sakoman
2012-01-30 20:09 ` Anders Darander
2012-01-30 20:29 ` Steve Sakoman
2012-01-30 17:14 ` [PATCH v3 3/3] zypper: add missing runtime dependences on gzip and gnupg Steve Sakoman
2012-01-30 17:17 ` [PATCH v3 0/3] *** SUBJECT HERE *** Steve Sakoman
2012-01-31 19:28 ` Darren Hart
2012-02-01 4:16 ` Steve Sakoman
2012-02-01 5:28 ` Wang, Shane
2012-02-01 6:57 ` Darren Hart [this message]
2012-02-01 6:53 ` Darren Hart
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=4F28E243.4040108@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=shane.wang@intel.com \
/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.