From: Seebs <seebs@seebs.net>
To: Trevor Woerner <twoerner@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv2] pseudo: use epoll API on Linux
Date: Mon, 18 Sep 2017 18:18:47 -0500 [thread overview]
Message-ID: <20170918181847.594b6943@seebsdell> (raw)
In-Reply-To: <CAHUNapTtXFnCurGoVtWKL=7v7Spxj4Hg2JqGh530ktRGgVgOyg@mail.gmail.com>
On Mon, 18 Sep 2017 19:16:13 -0400
Trevor Woerner <twoerner@gmail.com> wrote:
> It doesn't make sense to carry these large patches against pseudo in
> OE itself. Isn't pseudo one of the tools under The Yocto Project
> umbrella?
Yes. But the pool of people with the variety of expertise needed to
maintain it isn't huge, and *normally* I'm more responsive, I'm just
extra busy the last couple of months.
-s
next prev parent reply other threads:[~2017-09-18 23:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 13:34 [PATCHv2] pseudo: use epoll API on Linux Alexander Kanavin
2017-09-18 23:16 ` Trevor Woerner
2017-09-18 23:18 ` Seebs [this message]
2017-09-18 23:41 ` Trevor Woerner
2017-09-19 4:12 ` Seebs
2017-09-19 16:57 ` Trevor Woerner
2017-09-19 7:21 ` Burton, Ross
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=20170918181847.594b6943@seebsdell \
--to=seebs@seebs.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=twoerner@gmail.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