From: "Randy MacLeod" <randy.macleod@windriver.com>
To: Rahul Kumar <rahulk@mvista.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] bzip2: Add test suite for bzip2
Date: Tue, 14 Apr 2020 20:23:51 -0400 [thread overview]
Message-ID: <27d4dc4e-1d96-eadf-1023-1840dfdc8e55@windriver.com> (raw)
In-Reply-To: <CANv91vOGzdA52oLRuzDOB2hUA2dzeOb3vcMVO42F4T2iSSyRkA@mail.gmail.com>
On 2020-04-13 9:48 p.m., Rahul Kumar wrote:
> Hi Randy,
>
> Thanks for your feedback.
> As per your suggestion,I am working on that.
>
> currently my patch has Upstream-Status: Inappropriate.
>
> Since I am not aware of the patch submission process on bzip2, I posted
> a query on bzip2 mailing list (2 days back) but I did not get any
> response from there.
> If they are not responding, in this case shall i keep Upstream-Status:
> Inappropriate and send the v2 to oe-core Or should i wait for his
> response?
It's your call but I'd like to see:
Upstream-Status: Submitted.
as per:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status
Submitted [where]
- Submitted to upstream, waiting approval
- Optionally include where it was submitted,
such as the author, mailing list, etc.
> Or
> Do you have any idea how to submit the patch for bzip2-test repo.
No, I don't. If there's no answer, ping me here and we'll see if
someone can find a connection to the upstream developer(s).
../Randy
>
> *Thanks & Regards,*
> Rahul Kumar
> Software Engineer,Linux Solutions Engineering
> Group,Montavista Software LLC
> Email Id: rahulk@mvista.com <mailto:rahulk@mvista.com>
> <https://plus.google.com/+CodeTwoSoftware>
--
# Randy MacLeod
# Wind River Linux
prev parent reply other threads:[~2020-04-15 0:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 11:10 [PATCH] bzip2: Add test suite for bzip2 Rahul Kumar
2020-04-02 22:32 ` [OE-core] " Randy MacLeod
2020-04-13 17:22 ` Rahul Kumar
2020-04-13 19:18 ` Randy MacLeod
2020-04-14 1:48 ` Rahul Kumar
2020-04-15 0:23 ` Randy MacLeod [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=27d4dc4e-1d96-eadf-1023-1840dfdc8e55@windriver.com \
--to=randy.macleod@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rahulk@mvista.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