Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Buildhistory for the PACKAGE Reorder
Date: Fri, 22 Jun 2012 15:35:26 +0100	[thread overview]
Message-ID: <1747366.kqsrF4mgDg@helios> (raw)
In-Reply-To: <4FE0CB44.4030909@linux.intel.com>

On Tuesday 19 June 2012 11:56:04 Saul Wold wrote:
> On 06/19/2012 11:29 AM, Paul Eggleton wrote:
> > On Tuesday 19 June 2012 09:02:30 Saul Wold wrote:
> >> Please find attached the buildhistory_diff from 2 world builds with and
> >> without the PACKAGE Reorder.
> > 
> > Saul, would you mind pushing the buildhistory repo somewhere (e.g. to a
> > poky- contrib branch)? That would help me debug some of the weirdness in
> > the output there.
> 
> Sorry it is available, was mentioned in my past emails, its in the
> poky-contrib.git sgw/repack-buildhistory

Ah, sorry, didn't think to look there.

Upon closer inspection though it looks like the output you attached is the 
result of piping the output of buildhistory-diff through 'grep -v "PACKAGES 
changed order"' - which would explain the "duplicated" lines. By eliminating 
the lines containing that string you've also eliminated many lines that also 
contained the package name, and thus their items are concatenated underneath 
those for the previous package.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2012-06-22 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19 16:02 Buildhistory for the PACKAGE Reorder Saul Wold
2012-06-19 18:29 ` Paul Eggleton
2012-06-19 18:56   ` Saul Wold
2012-06-22 14:35     ` Paul Eggleton [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=1747366.kqsrF4mgDg@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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