From: Trevor Woerner <twoerner@gmail.com>
To: Ross Burton <ross.burton@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sstate: change "stamp is not reachable, removing manifests" message from info to debug
Date: Tue, 5 Jan 2016 14:15:29 -0500 [thread overview]
Message-ID: <568C1651.8060500@gmail.com> (raw)
In-Reply-To: <1451997165-25159-1-git-send-email-ross.burton@intel.com>
On 01/05/16 07:32, Ross Burton wrote:
> This code path has proven to work, so change the log level from info to debug so
> it doesn't spam the log in normal use.
I liked having this as part of the regular processing. If I only update
my upstream repositories once a week (for example) my next "bitbake ..."
would show which packages had upgrades. It was a cheap way of doing an
image diff, if you will.
In order to keep those messages now I would have to enable debug, which
will generate quite a lot more information.
Yes, I know I could get the "image diff" functionality by enabling
buildhistory and going that route, but as I said above this was sort of
a "cheap" image diff for free ;-)
prev parent reply other threads:[~2016-01-05 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 12:32 [PATCH] sstate: change "stamp is not reachable, removing manifests" message from info to debug Ross Burton
2016-01-05 19:15 ` Trevor Woerner [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=568C1651.8060500@gmail.com \
--to=twoerner@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.