Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Package upgrades
Date: Thu, 29 Mar 2018 23:30:37 -0400	[thread overview]
Message-ID: <20180330033037.GN2786@denix.org> (raw)
In-Reply-To: <c49fc448-a79d-1492-a5d9-398968aacd83@gmail.com>

On Thu, Mar 29, 2018 at 07:41:46PM -0700, Khem Raj wrote:
> On 3/29/18 7:34 PM, Denys Dmytriyenko wrote:
> >On Thu, Mar 29, 2018 at 06:38:58PM -0700, Khem Raj wrote:
> >>On Thu, Mar 29, 2018 at 5:17 PM, Denys Dmytriyenko <denis@denix.org> wrote:
> >>>On Thu, Mar 29, 2018 at 04:39:27PM -0700, Andre McCurdy wrote:
> >>>>On Thu, Mar 29, 2018 at 3:41 PM, Denys Dmytriyenko <denis@denix.org> wrote:
> >>>>>Ping. It's been 10 days - are there any issues with these updates?
> >>>>
> >>>>Only 10 days? :-)
> >>>
> >>>Yeah, I know, I'm too demanding... :)
> >>
> >>Ross does pick the patches from ml fairly quickly so always check
> >>
> >>http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=ross/mut
> >>
> >>or OE-Core's master-next
> >>
> >>http://git.openembedded.org/openembedded-core/log/?h=master-next
> >>
> >>from mut to master it might take a while since there are many patches coming in
> >>so integration takes time and sometimes there are issues with infra
> >>which can delay
> >>things,
> >
> >Yes, I'm quite aware of all the above - you don't have to mention all the
> >details to me.
> 
> I am glad thats the case. It was not clear from the message and some
> times this can be misconstrued.

You are absolutely right! After 10+ years in the OE community my mind and 
memory are not as sharp as they used to be - I keep forgetting things and do 
not communicate as clearly as before... :-P


> Still, it's a standard practice to inquire about own patches
> >once in a while. Especially since other similar non-critical updates are
> >merged right away. This is the only way to know if there were any issues with
> >the patches themselves, but Ross forgot or didn't have time to follow up yet.
> >
> >
> >>10 days seems pretty darn good in some cases its years see
> >>
> >>https://github.com/projectNe10/Ne10/pull/143
> >>
> >>in the end as long as it makes upstream.
> >
> >Heh, I don't think we should take that as an example to follow... :)
> >
> 


  reply	other threads:[~2018-03-30  3:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20  1:11 [PATCH 0/3] Package upgrades Denys Dmytriyenko
2018-03-20  1:11 ` [PATCH 1/3] lzip: upgrade 1.19 -> 1.20 Denys Dmytriyenko
2018-03-20  1:11 ` [PATCH 2/3] hdparm: upgrade 9.53 -> 9.55 Denys Dmytriyenko
2018-03-20  1:11 ` [PATCH 3/3] lz4: upgrade 1.7.4 -> 1.8.1.2 Denys Dmytriyenko
2018-03-29 22:41 ` [PATCH 0/3] Package upgrades Denys Dmytriyenko
2018-03-29 23:39   ` Andre McCurdy
2018-03-30  0:17     ` Denys Dmytriyenko
2018-03-30  1:38       ` Khem Raj
2018-03-30  2:34         ` Denys Dmytriyenko
2018-03-30  2:41           ` Khem Raj
2018-03-30  3:30             ` Denys Dmytriyenko [this message]
2018-03-30  8:36   ` Richard Purdie
  -- strict thread matches above, loose matches on Subject: below --
2015-05-11  6:48 [PATCH 0/3] Package Upgrades Robert Yang
2015-04-10  8:31 Robert Yang
2014-06-03  1:41 Chen Qi
2014-03-12  1:57 Chen Qi
2013-11-26 12:39 [PATCH 0/3] Package upgrades Cristiana Voicu
2013-10-24 18:29 Marko Lindqvist
2013-08-05  8:28 Cristiana Voicu
2012-12-10  8:08 Constantin Musca
2012-08-23 11:44 Constantin Musca
2012-08-24 18:36 ` Saul Wold
2012-08-14 12:50 Constantin Musca
2012-08-17 21:09 ` Saul Wold
2012-08-13 14:27 Constantin Musca
2012-08-17 20:56 ` Saul Wold

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=20180330033037.GN2786@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-core@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