From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] classes/buildhistory: do not save old packagehistory files by default
Date: Mon, 05 Dec 2011 22:48:14 +0000 [thread overview]
Message-ID: <1323125294.25960.106.camel@ted> (raw)
In-Reply-To: <8651be5fb600a2d20acaf3c7b6848f7855bd2b75.1323109431.git.paul.eggleton@linux.intel.com>
On Mon, 2011-12-05 at 18:28 +0000, Paul Eggleton wrote:
> Disable storing package history as version named files unless
> BUILDHISTORY_KEEP_VERSIONS is set to 1; otherwise the adds of these
> files that duplicate what is already in git anyway is just noise in the
> git log.
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
> meta/classes/buildhistory.bbclass | 9 +++++++--
> 1 files changed, 7 insertions(+), 2 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-12-05 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 18:28 [PATCH 0/1] buildhistory fix Paul Eggleton
2011-12-05 18:28 ` [PATCH 1/1] classes/buildhistory: do not save old packagehistory files by default Paul Eggleton
2011-12-05 22:48 ` Richard Purdie [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=1323125294.25960.106.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 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.