From: Peter Urbanec <openembedded-devel@urbanec.net>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: OE Core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V2] opkg: Call prerm and postrm scripts on package upgrade.
Date: Thu, 16 Oct 2014 09:34:23 +1100 [thread overview]
Message-ID: <543EF66F.7070809@urbanec.net> (raw)
In-Reply-To: <CANyK_8e3EV3dO72UJ6Bo=QodGS3A315j5E_i_7evPjrgGVqxgA@mail.gmail.com>
On 16/10/14 04:26, Paul Barker wrote:
> For the sake of future readers within OpenEmbedded, we need to make
> clearer here that this is opkg issue 104, not an OE issue number. This
> change isn't needed in the patch to opkg upstream though.
>
>> +
>> +Signed-off-by: Peter Urbanec <openembedded-devel@urbanec.net>
>
> Sorry to be pedantic but there's now 2 copies of the Signed-off-by
> line. If you resend this, I'd also bring the Upstream-status line down
> so that it immediately follows the Signed-off-by line. That's just a
> minor cosmetic point though, it may be possible for someone to make
> these edits as the patch is merged.
I resent the patch with your suggestions incorporated. Specifically, I
mentioned that the patch is for an opkg issue and provided the URL to
the relevant opkg issue tracker entry. I also rearranged the
Upstream-Status and Signed-off-by lines as suggested.
> This looks fine. As I've said in reply to the patch on the opkg-devel
> mailing list, I'm busy this week but should have time to test this
> properly next week. It looks correct to me though, the logic is almost
> identical to the patch I prepared which covers prerm only.
>
> It probably doesn't need to wait for my test before going into OE though.
Thanks. Version 3 of the patch I sent out has no code changes, just the
patch meta information and comments.
Cheers,
Peter
next prev parent reply other threads:[~2014-10-15 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <543ea179.e25bb40a.2c8a.1e34SMTPIN_ADDED_BROKEN@mx.google.com>
2014-10-15 17:26 ` [PATCH V2] opkg: Call prerm and postrm scripts on package upgrade Paul Barker
2014-10-15 22:34 ` Peter Urbanec [this message]
2014-10-15 16:31 Peter Urbanec
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=543EF66F.7070809@urbanec.net \
--to=openembedded-devel@urbanec.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
/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.