From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Patchwork hooks for meta-oe active and working
Date: Mon, 17 Oct 2011 05:04:58 -0400 [thread overview]
Message-ID: <20111017090458.GO26170@denix.org> (raw)
In-Reply-To: <j7gllt$s0$1@dough.gmane.org>
On Mon, Oct 17, 2011 at 09:32:13AM +0200, Koen Kooi wrote:
> Thanks to Khem the patchwork hooks for meta-oe (and hence meta-efl,
> meta-gnome and meta-xfce) are active and working.
> Once the commits hit the OE server the state will get updated automatically,
> so the submitter will instantly know when his/her patch has hit the repo.
Great! Thanks a lot for such a nice feature!
--
Denys
next prev parent reply other threads:[~2011-10-17 9:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 7:32 Patchwork hooks for meta-oe active and working Koen Kooi
2011-10-17 9:04 ` Denys Dmytriyenko [this message]
2011-10-17 11:05 ` Anders Darander
2011-10-18 20:38 ` Patchwork breaking submitters name Was: " Martin Jansa
2011-10-18 20:49 ` Khem Raj
2011-10-18 21:10 ` Martin Jansa
2011-10-18 21:36 ` Khem Raj
2011-10-18 21:42 ` Martin Jansa
2011-10-18 22:01 ` Khem Raj
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=20111017090458.GO26170@denix.org \
--to=denis@denix.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