All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Stefan Agner <stefan@agner.ch>
Cc: Stefan Agner <stefan.agner@toradex.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 0/3] postinst fixes for opgk/dpkg
Date: Thu, 14 Jun 2018 22:08:52 +0300	[thread overview]
Message-ID: <CANNYZj_0cKie+XytpFL_qQ2oS_K4kBQL226CFkybqSwujOy_GQ@mail.gmail.com> (raw)
In-Reply-To: <72038ce45486336b7f3d611d7181e95f@agner.ch>

No need to be nervous. The patch will make it in; patches do not get
quietly rejected. If it hasn't showed up yet, it's most likely because
the patch will be tested on the autobuilder in a separate set from the
'regular patches', or (yes, this happens) it has slipped through the
cracks. In that case (I know it's impossible to tell from the
outside), just resend again.

Also, please do help us out with oe-core patch review and recipe
maintenance, particularly updating them to latest versions.


Alex

2018-06-14 16:57 GMT+03:00 Stefan Agner <stefan@agner.ch>:
> On 04.06.2018 18:18, Alexander Kanavin wrote:
>> 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."
>>
>
> Gentle ping on that again.
>
> This week it read:
> "Due to the milestone, patch merging is slowing to stabilize."
>
> Also, there have been patches merged which were posted after this
> patchset... It is really rather important for us since it is hard to fix
> in lower layers...
>
> So I am getting nervous whether it still makes it?
>
> --
> Stefan
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core


      reply	other threads:[~2018-06-14 19:08 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
2018-06-14 13:57     ` Stefan Agner
2018-06-14 19:08       ` Alexander Kanavin [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=CANNYZj_0cKie+XytpFL_qQ2oS_K4kBQL226CFkybqSwujOy_GQ@mail.gmail.com \
    --to=alex.kanavin@gmail.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.