Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [STABLE][PATCH] gsoap: actually stage headers and	libraries..
Date: Wed, 08 Apr 2009 16:12:38 -0400	[thread overview]
Message-ID: <20090408201238.GI14502@denix.org> (raw)
In-Reply-To: <49DD0366.8000202@bolloretelecom.eu>

On Wed, Apr 08, 2009 at 10:04:54PM +0200, Jeremy Lain? wrote:
> > Overall it looks Ok to me. But I have 2 questions about a proper procedure:
> > - should the .dev have the same fix?
> > - should PR be incremented by 1?
> 
> Yes, the dev branch has the exact same .bb file. In fact the patch is simply the diff
> between stable and dev.

Sorry, I missed it in .dev - both questions retracted.

Acked-by: Denys Dmytriyenko <denis@denix.org>

-- 
Denys



      reply	other threads:[~2009-04-08 20:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 16:48 [STABLE][PATCH] gsoap: actually stage headers and libraries Jeremy Lainé
2009-04-08  0:45 ` Denys Dmytriyenko
2009-04-08  9:21   ` Jeremy Lainé
2009-04-08 18:58     ` Denys Dmytriyenko
2009-04-08 20:04       ` Jeremy Lainé
2009-04-08 20:12         ` Denys Dmytriyenko [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=20090408201238.GI14502@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox