From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Vignesh Rajendran (RBEI/ECF3)" <Vignesh.Rajendran@in.bosch.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] package.bbclass: provide debug sources in externalsrc -dbg packages
Date: Wed, 16 May 2018 15:53:40 +0300 [thread overview]
Message-ID: <f856913e-77b1-e6d8-7fa3-7dd781714f17@linux.intel.com> (raw)
In-Reply-To: <44ef14450ded42d4a6d74278de3ca3ad@in.bosch.com>
On 05/16/2018 03:11 PM, Vignesh Rajendran (RBEI/ECF3) wrote:
> As I am new to the patch submission, anyone can explain how long this
> process will take for acceptance in master/next release?
>
> After several days of waiting by watching OE-mailing thread for any
> reply for the patch, Now I had a feeling like the patch may have been
> missed.
Generally we don't positively acknowledge the patches, to reduce the
amount of noise on the mailing list. If the patch doesn't show up in
master after a week or two, do ping or resend.
Alex
next prev parent reply other threads:[~2018-05-16 13:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 5:50 [meta-oe][PATCH] package.bbclass: provide debug sources in externalsrc -dbg packages Vignesh Rajendran
2018-05-16 12:11 ` Vignesh Rajendran (RBEI/ECF3)
2018-05-16 12:53 ` Alexander Kanavin [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-17 5:50 Vignesh Rajendran
2018-05-17 5:55 ` Vignesh Rajendran (RBEI/ECF3)
2018-05-20 22:26 ` Paul Eggleton
2018-05-21 4:50 ` Vignesh Rajendran (RBEI/ECF3)
2018-06-18 6:38 ` Vignesh Rajendran (RBEI/ECF3)
2018-06-18 17:43 ` Khem Raj
2018-06-19 4:54 ` Vignesh Rajendran (RBEI/ECF3)
2018-07-06 4:29 ` Vignesh Rajendran (RBEI/ECF3)
2018-07-06 4:50 ` Khem Raj
2018-07-12 7:00 ` Vignesh Rajendran (RBEI/ECF3)
2018-07-23 10:02 ` Vignesh Rajendran (RBEI/ECF3)
2018-07-30 4:46 ` Vignesh Rajendran (RBEI/ECF3)
2018-08-10 5:36 ` Vignesh Rajendran (RBEI/ECF3)
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=f856913e-77b1-e6d8-7fa3-7dd781714f17@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=Vignesh.Rajendran@in.bosch.com \
--cc=openembedded-core@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