From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 6/9] scripts: add buildhistory-tag script
Date: Thu, 02 Aug 2012 11:49:10 +0100 [thread overview]
Message-ID: <40727268.akUMmXJU4Z@helios> (raw)
In-Reply-To: <CAJTo0LZ7QJtfzmsg2a++ay8YoNOptRFohWwQrKNT0JrHYkYRbw@mail.gmail.com>
On Thursday 02 August 2012 11:18:20 Burton, Ross wrote:
> On 2 August 2012 10:23, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
> > This trivial script determines BUILDHISTORY_DIR using bitbake and then
> > passes the command line options to "git tag" on the buildhistory
> > repository. This is useful for setting a tag before making some changes;
> > even if the build takes a number of executions of bitbake (resulting in
> > multiple commits to the buildhistory repository) you can still do the
> > overall comparison easily.
> >
> > Suggested by Ross Burton <ross.burton@intel.com>.
>
> I've since changed my local script to be "buildhistory" that just runs
> git "$@", so "buildhistory log" etc work nicely.
Interesting - sounds like it would be useful, but I wonder how it would then
fit in with buildhistory-diff as a separate script (particularly with diff as a
valid option to "buildhistory")...
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-08-02 11:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 9:23 [PATCH 0/9] buildhistory improvements Paul Eggleton
2012-08-02 9:23 ` [PATCH 1/9] classes/buildhistory: remove obsolete flat package history feature Paul Eggleton
2012-08-02 9:23 ` [PATCH 2/9] classes/buildhistory: ensure old package info is removed Paul Eggleton
2012-08-02 9:23 ` [PATCH 3/9] classes/buildhistory: remove unused functions Paul Eggleton
2012-08-02 9:23 ` [PATCH 4/9] classes/buildhistory: save preinst/postinst/prerm/postrm Paul Eggleton
2012-08-02 9:23 ` [PATCH 5/9] classes/buildhistory: record PKG/PKGE/PKGV/PKGR Paul Eggleton
2012-08-02 9:23 ` [PATCH 6/9] scripts: add buildhistory-tag script Paul Eggleton
2012-08-02 10:18 ` Burton, Ross
2012-08-02 10:49 ` Paul Eggleton [this message]
2012-08-02 11:12 ` Burton, Ross
2012-08-02 9:23 ` [PATCH 7/9] buildhistory_analysis: tidy up duplicate split_version function Paul Eggleton
2012-08-02 9:23 ` [PATCH 8/9] buildhistory_analysis: ignore removal of self-dependencies Paul Eggleton
2012-08-02 9:23 ` [PATCH 9/9] classes/buildhistory: save metadata revisions Paul Eggleton
2012-08-02 11:27 ` [PATCH 0/9] buildhistory improvements Burton, Ross
2012-08-02 12:58 ` Martin Jansa
2012-08-02 16:14 ` Andreas Müller
2012-08-06 14:29 ` Richard Purdie
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=40727268.akUMmXJU4Z@helios \
--to=paul.eggleton@linux.intel.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.