From: Saul Wold <sgw@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] log_srcrev.bbclass: add a bbclass for logging SRCREVs
Date: Tue, 26 Feb 2013 09:25:08 -0800 [thread overview]
Message-ID: <512CEFF4.8030000@linux.intel.com> (raw)
In-Reply-To: <CAP9ODKqfv-8=MG=ffQQG_DSTxj9=059Z_W4mPznQiwsKKaYM-w@mail.gmail.com>
On 02/26/2013 08:56 AM, Otavio Salvador wrote:
> On Tue, Feb 26, 2013 at 12:04 PM, Constantin Musca
> <constantinx.musca@intel.com> wrote:
>> - add a task which creates a file for each package with the following
>> format:
>>
>> ${BB_FILENAME},${SRC_URI},${SRCREV},${FROM_AUTOREV}
>>
>> [YOCTO #3041]
>>
>> Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
>
> What is the use-case for this?
>
I could reply with see bug #3041!
There is a need to have the actual SRCREVs from AUTOREV'ed package
version, so a build can be reproduced at a later date or so you know
what SRCREV went into a given release.
Sau!
next prev parent reply other threads:[~2013-02-26 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 15:04 [PATCH v2] log_srcrev.bbclass: add a bbclass for logging SRCREVs Constantin Musca
2013-02-26 16:56 ` Otavio Salvador
2013-02-26 17:25 ` Saul Wold [this message]
2013-02-26 17:33 ` Otavio Salvador
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=512CEFF4.8030000@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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