From: Denys Dmytriyenko <denis@denix.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-qt5] commits w/o patches on the list?
Date: Mon, 15 Oct 2018 01:42:33 -0400 [thread overview]
Message-ID: <20181015054233.GD7186@denix.org> (raw)
In-Reply-To: <CAMKF1soJ_zWahqTPNYeqqwQsRUdEpYL+GiFKziWfZYK6MrTN7g@mail.gmail.com>
On Sun, Oct 14, 2018 at 10:04:51PM -0700, Khem Raj wrote:
> On Sun, Oct 14, 2018 at 8:46 PM Denys Dmytriyenko <denis@denix.org> wrote:
> >
> > I noticed there are commits to meta-qt5 that didn't have corresponding patches
> > sent to the list and didn't have any discussions around those. Is that the new
> > norm?
>
> in a way yes. meta-qt5 has recently started to accept github pull requests.
well, that's something for another discussion...
for now, I'm trying to locate a PR/patch for this commit:
https://github.com/meta-qt5/meta-qt5/commit/3224b028e70ab3a910ce4fccdd9f3fac4e37011f
--
Denys
prev parent reply other threads:[~2018-10-15 5:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 3:46 [meta-qt5] commits w/o patches on the list? Denys Dmytriyenko
2018-10-15 5:04 ` Khem Raj
2018-10-15 5:42 ` Denys Dmytriyenko [this message]
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=20181015054233.GD7186@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@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