Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Jose Lamego <jose.a.lamego@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Cc: Tom Rini <trini@konsulko.com>,
	Patrick Ohly <patrick.ohly@intel.com>,
	Michael Halstead <michael@yoctoproject.org>
Subject: Re: meta-openembedded patchwork git hook
Date: Wed, 30 Nov 2016 12:41:20 -0600	[thread overview]
Message-ID: <53ca2ead-1b75-ff6d-30c1-abb16330bad3@linux.intel.com> (raw)
In-Reply-To: <19E9BF3F-664F-42A4-A170-5B7BB473ED80@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2480 bytes --]



On 11/29/2016 07:50 PM, Khem Raj wrote:
> 
>> On Nov 29, 2016, at 2:34 PM, Jose Lamego <jose.a.lamego@linux.intel.com> wrote:
>>
>>
>>
>> On 11/29/2016 02:43 PM, Tom Rini wrote:
>>> On Wed, Nov 30, 2016 at 06:52:46AM +1300, Paul Eggleton wrote:
>>>
>>>> Hi folks,
>>>>
>>>> Martin just brought to my attention that the git hook for the 
>>>> meta-openembedded repository that's supposed to update patchwork still isn't 
>>>> working and hasn't done so for a very long time. I thought we'd fixed this so 
>>>> that merged patches get marked as "Accepted", but at least for meta-
>>>> openembedded it seems like that's not the case.
>>>>
>>>> Jose / Michael - can you look into this if you haven't already? Please let me 
>>>> know if you need any help.
>>
>> The git hook was configured to update OE-core only, Michael will help us
>> to include meta-openembedded.
>>
> 
> There are more repos using patchwork beyond OE-core and meta-opemebedded
> please enable it for all of them  as well.
> 

Now all of the projects are enabled to receive automatic updates from
the git-hook (Thanks Michael). Please let me know if any undesired
behavior is detected.

>>>
>>> Since I brought this up on IRC, I wanted to chime in here.  First, if
>>> you want to use top-of-tree patchwork you'll also want to grab
>>> https://patchwork.ozlabs.org/bundle/stephenfin/post-receive%20fixes/
>>
>>
>> Hi Tom, nice meeting you. OE-Patchwork is using a fork in [1] from
>> freedesktop.org's patchwork at [2]. I will look at the hook fixes you
>> mentioned at the first chance, thanks for the tip.
>>
>>> (and fwiw, I also have been setting the DJANGO part to 'dev' rather than
>>> production for my use-case).  Second, I think part of the problem is
>>> that there are just some cases where the hashing fails, which for me is
>>> around 10% of the time.  Depending on how much one uses bundles and
>>> tracks what ends up being committed this may or may not be a problem.
>>> And I'm sure upstream patchwork would appreciate any changes to improve
>>> hashing success :)
>>>
>>
>> Regards
>> Jose
>>
>> -- 
>> Jose Lamego | OTC Embedded Platforms & Tools | GDC
>>
>> -- 
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> 

-- 
Jose Lamego | OTC Embedded Platforms & Tools | GDC


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 501 bytes --]

  reply	other threads:[~2016-11-30 18:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 17:52 meta-openembedded patchwork git hook Paul Eggleton
2016-11-29 20:43 ` Tom Rini
2016-11-29 22:34   ` Jose Lamego
2016-11-30  1:50     ` Khem Raj
2016-11-30 18:41       ` Jose Lamego [this message]
2016-12-02  8:30         ` Martin Jansa
2016-12-02 12:29           ` Tom Rini
2016-12-02 15:45             ` Jose Lamego
2016-12-09 11:09               ` Martin Jansa
2016-12-14 20:27               ` Jose Lamego
2016-12-14 21:02                 ` Jose Lamego

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=53ca2ead-1b75-ff6d-30c1-abb16330bad3@linux.intel.com \
    --to=jose.a.lamego@linux.intel.com \
    --cc=michael@yoctoproject.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=patrick.ohly@intel.com \
    --cc=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox