Poky Project Discussions
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/2] Revised summary & description patch
Date: Thu, 03 Feb 2011 12:00:08 -0800	[thread overview]
Message-ID: <4D4B0948.7040802@intel.com> (raw)
In-Reply-To: <cover.1296761455.git.mark.hatle@windriver.com>

On 02/03/2011 11:32 AM, Mark Hatle wrote:
> This is an update pull request for the revised summary&  description
> patch.  It stop the failure mentioned by Saul in a previous email.
>
> The second chunk of the patch is new and includes the workaround I sent
> earlier today on the prelink documentation issue.  I'm not sure this is
> really the right patch, but it should unblock people.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
>    Branch: mhatle/wrsync
>    Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/wrsync
>
> Thanks,
>      Mark Hatle<mark.hatle@windriver.com>
> ---
>
>
> Mark Hatle (2):
>    bitbake.conf&  package.bbclass: Use default SUMMARY and DESCRIPTION
>    Docbook workaround
>
>   meta/classes/package.bbclass                 |    5 +++-
>   meta/conf/bitbake.conf                       |   30 +++++++++++++++++++-------
>   meta/recipes-devtools/prelink/prelink_git.bb |    5 ++++
>   3 files changed, 31 insertions(+), 9 deletions(-)
>
Mark,

I merged the SUMMARY & DESCRIPTION changes, but held off on the 
workaround to give Scott G. a chance to fix it properly.

Thanks

Sau!



      parent reply	other threads:[~2011-02-03 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03 19:32 [PATCH 0/2] Revised summary & description patch Mark Hatle
2011-02-03 19:32 ` [PATCH 1/2] bitbake.conf & package.bbclass: Use default SUMMARY and DESCRIPTION Mark Hatle
2011-02-03 19:32 ` [PATCH 2/2] Docbook workaround Mark Hatle
2011-02-03 20:00 ` Saul Wold [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=4D4B0948.7040802@intel.com \
    --to=saul.wold@intel.com \
    --cc=mark.hatle@windriver.com \
    --cc=poky@yoctoproject.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