Poky Project Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Chris Larson <clarson@kergoth.com>, poky@yoctoproject.org
Subject: Re: [PATCH 0/3] logging updates
Date: Fri, 06 May 2011 15:37:41 -0700	[thread overview]
Message-ID: <4DC47835.40802@linux.intel.com> (raw)
In-Reply-To: <cover.1303760083.git.dvhart@linux.intel.com>

On 04/25/2011 12:36 PM, Darren Hart wrote:
> The first two patches fix issues in the existing bash logging infrastructure.
> The third proposes a new bash logging mechanism.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
>    Branch: dvhart/logging
>    Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/logging
>
> Thanks,
>      Darren Hart<dvhart@linux.intel.com>
> ---
>
>
> Darren Hart (3):
>    logging: fix oedebug loglevel test
>    logging: remove unused BBDEBUG from local.conf.sample
>    logging: add bb* logging mechanisms for bash recipe functions
>
>   meta-yocto/conf/local.conf.sample |    2 -
>   meta/classes/base.bbclass         |    9 +++--
>   meta/classes/logging.bbclass      |   72 +++++++++++++++++++++++++++++++++++++
>   3 files changed, 77 insertions(+), 6 deletions(-)
>   create mode 100644 meta/classes/logging.bbclass
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Pulled int Master

Thanks
	Sau!


      parent reply	other threads:[~2011-05-06 22:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-25 19:36 [PATCH 0/3] logging updates Darren Hart
2011-04-25 19:36 ` [PATCH 1/3] logging: fix oedebug loglevel test Darren Hart
2011-04-25 19:36 ` [PATCH 2/3] logging: remove unused BBDEBUG from local.conf.sample Darren Hart
2011-04-25 19:36 ` [PATCH 3/3] logging: add bb* logging mechanisms for bash recipe functions Darren Hart
2011-05-06 22:37 ` 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=4DC47835.40802@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=clarson@kergoth.com \
    --cc=dvhart@linux.intel.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