From: Adrian Bunk <bunk@stusta.de>
To: "Slater, Joseph" <joe.slater@windriver.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] libtool: allow for use of reproducible_build bbclass
Date: Fri, 12 Jul 2019 09:30:40 +0300 [thread overview]
Message-ID: <20190712063040.GB2092@localhost> (raw)
In-Reply-To: <007BD92917A2324FA403BCF9A464CF84FA81B717@ALA-MBD.corp.ad.wrs.com>
On Fri, Jul 12, 2019 at 01:51:26AM +0000, Slater, Joseph wrote:
> That's a question I have about things like this, where some information seems of minimal use, but is there and is now malignant. Chuck it or modify it to be benign.
All such patches should be submitted upstream, and the final decision
for that would be whatever upstream prefers.
If in doubt, I would start with whatever is the simplest correct change.
It is unlikely that someone will insist on keeping marginally relevant
information like in this case.
Debian has already done a lot of work regarding reproducible,
so checking there for existing patches first is always a good idea.
> Joe
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-07-12 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 20:27 [PATCH 1/1] libtool: allow for use of reproducible_build bbclass Joe Slater
2019-07-11 20:44 ` Adrian Bunk
2019-07-11 21:55 ` Burton, Ross
2019-07-12 1:51 ` Slater, Joseph
2019-07-12 6:30 ` Adrian Bunk [this message]
2019-07-12 8:33 ` Burton, Ross
2019-07-12 9:19 ` Adrian Bunk
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=20190712063040.GB2092@localhost \
--to=bunk@stusta.de \
--cc=joe.slater@windriver.com \
--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.