Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] buildhistory: remove duplicate entries from dot graph
Date: Tue, 20 Mar 2012 11:48:55 +0000	[thread overview]
Message-ID: <1812139.SkpSglmEkv@helios> (raw)
In-Reply-To: <1332241255-5083-3-git-send-email-koen@dominion.thruhere.net>

On Tuesday 20 March 2012 12:00:55 Koen Kooi wrote:
> There are various conditions that lead to duplicate entries in the dot graph
> which need to get fixed, but this patch is a catchall.

Dependencies and recommends are already de-duped - are we getting duplicates 
in the package list as well?

> Another benefit is that the sort order is now know, leading to less spurious
> diffs in buildhistory commits.

The package list is already sorted, and so are the dependencies and 
recommends, so how would the sort order be changing?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-03-20 11:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 11:00 [PATCH 1/3] buildhistory: record all builds Koen Kooi
2012-03-20 11:00 ` [PATCH 2/3] buildhistory: make seperate commits for every entry in the buildhistory dir Koen Kooi
2012-03-20 11:00 ` [PATCH 3/3] buildhistory: remove duplicate entries from dot graph Koen Kooi
2012-03-20 11:48   ` Paul Eggleton [this message]
2012-03-20 12:11     ` Koen Kooi
2012-03-20 13:14       ` Paul Eggleton
2012-03-20 13:40         ` Koen Kooi

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=1812139.SkpSglmEkv@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=koen@dominion.thruhere.net \
    --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