From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] lib/bb/build: create .old symlink for run.do_xx and log.do_xx
Date: Tue, 06 Sep 2016 14:19:17 +0100 [thread overview]
Message-ID: <1473167957.20226.44.camel@linuxfoundation.org> (raw)
In-Reply-To: <1473162780-11643-1-git-send-email-nicolas.dechesne@linaro.org>
On Tue, 2016-09-06 at 12:53 +0100, Nicolas Dechesne wrote:
> When they exist, keep a reference to the 'previous' (or old) build
> for run.do_xx
> and log.do_xx files, which can be useful when debugging. The symlink
> are created
> as run.do_xx.old and log.do_xx.old.
>
> Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
> ---
> lib/bb/build.py | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
We keep the old logfiles around and "ls -t" is comparatively straight
forward. Do we really need this extra complexity?
Cheers,
Richard
next prev parent reply other threads:[~2016-09-06 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 11:53 [PATCH] lib/bb/build: create .old symlink for run.do_xx and log.do_xx Nicolas Dechesne
2016-09-06 13:19 ` Richard Purdie [this message]
2016-09-06 13:26 ` Nicolas Dechesne
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=1473167957.20226.44.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=nicolas.dechesne@linaro.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.