From: Tom Rini <trini@konsulko.com>
To: openembedded-devel@lists.openembedded.org
Cc: Patrick Ohly <patrick.ohly@intel.com>,
Michael Halstead <michael@yoctoproject.org>,
Jose Lamego <jose.a.lamego@intel.com>
Subject: Re: meta-openembedded patchwork git hook
Date: Tue, 29 Nov 2016 15:43:27 -0500 [thread overview]
Message-ID: <20161129204327.GG2546@bill-the-cat> (raw)
In-Reply-To: <4717571.f7GXZOAcRz@peggleto-mobl.ger.corp.intel.com>
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.
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/
(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 :)
--
Tom
next prev parent reply other threads:[~2016-11-29 20:43 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 [this message]
2016-11-29 22:34 ` Jose Lamego
2016-11-30 1:50 ` Khem Raj
2016-11-30 18:41 ` Jose Lamego
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=20161129204327.GG2546@bill-the-cat \
--to=trini@konsulko.com \
--cc=jose.a.lamego@intel.com \
--cc=michael@yoctoproject.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=patrick.ohly@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.