Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alejandro Enedino Hernandez Samaniego
	<alejandro.enedino.hernandez-samaniego@xilinx.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] python3: Improve logging capabilities for do_create_manifest
Date: Tue, 03 Apr 2018 11:08:44 +0100	[thread overview]
Message-ID: <1522750124.11431.232.camel@linuxfoundation.org> (raw)
In-Reply-To: <1522749884.11431.231.camel@linuxfoundation.org>

On Tue, 2018-04-03 at 11:04 +0100, Richard Purdie wrote:
> On Mon, 2018-04-02 at 13:08 -0700, Alejandro Enedino Hernandez
> Samaniego wrote:
> > 
> > Adds a couple of prints to get a nicer log, and creates a
> > small summary or report after checking every module, it
> > makes it more feasible for adoption, easier to debug why
> > a module ended at a certain package and see how the
> > manifest was created.
> > 
> > Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xili
> > nx
> > .com>
> Can you rebase against master please as this clashes with one of your
> other changes which already merged!

Actually, I have it applied now, thanks.

Richard


  reply	other threads:[~2018-04-03 10:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-02 20:08 [PATCH] python3: Improve logging capabilities for do_create_manifest Alejandro Enedino Hernandez Samaniego
2018-04-02 21:05 ` ✗ patchtest: failure for " Patchwork
2018-04-03 10:04 ` [PATCH] " Richard Purdie
2018-04-03 10:08   ` Richard Purdie [this message]
2018-04-03 17:59     ` Alejandro Enedino Hernandez Samaniego

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=1522750124.11431.232.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alejandro.enedino.hernandez-samaniego@xilinx.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox