Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Michael Halstead <michael@yoctoproject.org>
Subject: Re: checking if a patch was approved
Date: Tue, 27 Oct 2015 13:00:16 +0100	[thread overview]
Message-ID: <20151027120016.GC2577@jama> (raw)
In-Reply-To: <11758297.Qg5HCuaF4n@peggleto-mobl.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1815 bytes --]

On Tue, Oct 27, 2015 at 11:37:36AM +0000, Paul Eggleton wrote:
> On Tuesday 27 October 2015 08:12:48 Nicolas Dechesne wrote:
> > On Tue, Oct 27, 2015 at 12:12 AM, Ivan Sergio Borgonovo
> > <mail@webthatworks.it> wrote:
> > > I saw many patch passing by and I submitted a couple about
> > > meta-toolchain-qt5.
> > > I didn't see any message from Otavio or Martin "approving" a patches.
> > > 
> > > How can I check if it was approved other than pulling from the
> > > repo/checking github?
> > > 
> > > Or if there is no place to check... consider this a ping ;)
> > 
> > all commits are published on
> > openembedded-commits@lists.openembedded.org mailing list, and in
> > general you see when it's pushed in master-next, then in master.. i
> > have a mail filter that checks my name there.. it's the poor man
> > solution.. but it works. Note that the email trigger has been broken
> > for 2 weeks.. but i suspect this is a temporary issue that should be
> > fixed..
> 
> FWIW there are a small number of us working on improving patchwork so that 
> we're able to rely upon the results it shows as being the outstanding patches 
> in the queue and potentially even send email notifications to submitters (opt-
> in). I'd also like to go a step further and trigger some automatic validation 
> on patches. At the moment we're trying to figure out if we're able to spend the 
> time working on this in the next development cycle.

Paul: do you know what's wrong with git hooks triggering
openembedded-commits e-mails? Or maybe it's the ML itself, but there
was no e-mail in last month. I've pinged Michael on IRC twice (+CC here)

http://lists.openembedded.org/pipermail/openembedded-commits/2015-September/thread.html

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-10-27 11:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 23:12 checking if a patch was approved Ivan Sergio Borgonovo
2015-10-27  7:12 ` Nicolas Dechesne
2015-10-27 10:40   ` Ivan Sergio Borgonovo
2015-10-27 10:47     ` Otavio Salvador
2015-10-27 11:05     ` Martin Jansa
2015-10-28 10:20       ` Ivan Sergio Borgonovo
2015-10-27 11:37   ` Paul Eggleton
2015-10-27 12:00     ` Martin Jansa [this message]
2015-10-27 12:48       ` Paul Eggleton

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=20151027120016.GC2577@jama \
    --to=martin.jansa@gmail.com \
    --cc=michael@yoctoproject.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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