All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 4/4] webkitgtk: Add reproducibility fix
Date: Tue, 4 Jan 2022 16:44:57 +0100	[thread overview]
Message-ID: <6197f2dd-4e78-3a52-5513-0d166187cb2e@theobroma-systems.com> (raw)
In-Reply-To: <20220104141625.1369719-4-richard.purdie@linuxfoundation.org>

Hi Richard,

On 1/4/22 15:16, Richard Purdie wrote:
> When the date rolled from one year to another this highlighted a reproducibility
> issue. This could be better fixed by using SOURCE_DATE_EPOCH from the environment
> but I'm not sure how you do that in ruby. Help from someone with that knowledge
> to submit that upstream very welcome.
> 

Small side note, it seems like "copyright years" aren't actually any 
useful, see https://hynek.me/til/copyright-years/ and 
https://www.linuxfoundation.org/blog/copyright-notices-in-open-source-software-projects/.

I guess we can just notify the project to stop using the date entirely 
in the copyright to avoid those issues and hope they'll just agree :)

Cheers,
Quentin


  reply	other threads:[~2022-01-04 15:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 14:16 [PATCH 1/4] package_deb/ipk/rpm: Add more minimal do_build dependencies back Richard Purdie
2022-01-04 14:16 ` [PATCH 2/4] meson: Handle qemu riscv issues Richard Purdie
2022-01-04 14:16 ` [PATCH 3/4] openssl: Add reproducibility fix Richard Purdie
2022-01-04 14:16 ` [PATCH 4/4] webkitgtk: " Richard Purdie
2022-01-04 15:44   ` Quentin Schulz [this message]
2022-01-04 16:25   ` [OE-core] " Khem Raj

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=6197f2dd-4e78-3a52-5513-0d166187cb2e@theobroma-systems.com \
    --to=quentin.schulz@theobroma-systems.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.