All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Urbanec <openembedded-devel@urbanec.net>
To: OE Core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] opkg: Call prerm and postrm scripts on package upgrade.
Date: Thu, 16 Oct 2014 03:39:30 +1100	[thread overview]
Message-ID: <543EA342.40003@urbanec.net> (raw)
In-Reply-To: <CANyK_8ekCtKhA6Ps7tyP8PxerCpP_iDFqBbsCiuB1q_NTFJyaA@mail.gmail.com>

On 16/10/14 00:17, Paul Barker wrote:
>
> This is still missing "Upstream-status:"
...
>> + }
>> + + static int
>
> I don't think the patch has been generated properly here. There
> shouldn't be a change to this line.

Patch resent. I moved the Upstream-status: from the header of the patch, 
into the header of the embedded patch. I hope I got it right!

As far as the patch corruption is concerned, that's Thunderbird 31 being 
helpful, even though I asked it not to interfere. I resent the patch 
using a webmail client, which seems to have done a better job.

Cheers,

	Peter



      reply	other threads:[~2014-10-15 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 11:49 [PATCH 1/2] opkg: Call prerm and postrm scripts on package upgrade Peter Urbanec
2014-10-15 13:17 ` Paul Barker
2014-10-15 16:39   ` Peter Urbanec [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=543EA342.40003@urbanec.net \
    --to=openembedded-devel@urbanec.net \
    --cc=openembedded-core@lists.openembedded.org \
    /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.