All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Stefan Agner <stefan@agner.ch>, openembedded-core@lists.openembedded.org
Cc: Stefan Agner <stefan.agner@toradex.com>
Subject: Re: [PATCH v2 0/3] postinst fixes for opgk/dpkg
Date: Mon, 4 Jun 2018 19:18:00 +0300	[thread overview]
Message-ID: <bbbf2ec8-8c75-5195-b0ff-475c499853e3@linux.intel.com> (raw)
In-Reply-To: <84556032da03a0e29a955e347028db45@agner.ch>

On 06/04/2018 07:06 PM, Stefan Agner wrote:

> Anything holding us back merging this changes?

Please read the Yocto project status mail:

" ·         Patch review/merging was slow over the past week due to Ross 
being on vacation and changes in Richard’s employment/hardware situation 
but at least some of the backlog was resolved over the weekend and the 
hardware issues should be worked around now."

Alex


  reply	other threads:[~2018-06-04 16:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16  9:13 [PATCH v2 0/3] postinst fixes for opgk/dpkg Stefan Agner
2018-05-16  9:13 ` [PATCH v2 1/3] opkg: avoid running postinst scripts twice when using systemd Stefan Agner
2018-05-16  9:13 ` [PATCH v2 2/3] run-postinsts: for dpkg/opkg, do not rely on /etc/*-postinsts Stefan Agner
2018-05-16  9:13 ` [PATCH v2 3/3] rootfs.py: for dpkg/opkg, don't install postinsts if package management is present Stefan Agner
2018-06-04 16:06 ` [PATCH v2 0/3] postinst fixes for opgk/dpkg Stefan Agner
2018-06-04 16:18   ` Alexander Kanavin [this message]
2018-06-14 13:57     ` Stefan Agner
2018-06-14 19:08       ` Alexander Kanavin

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=bbbf2ec8-8c75-5195-b0ff-475c499853e3@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=stefan.agner@toradex.com \
    --cc=stefan@agner.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.