From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>, Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: jn/reproducible-build, was Re: What's cooking in git.git (Nov 2017, #08; Tue, 28)
Date: Fri, 1 Dec 2017 15:32:07 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1712011526490.98586@virtualbox> (raw)
In-Reply-To: <xmqq1skh6fyz.fsf@gitster.mtv.corp.google.com>
Hi Junio & Jonathan (Nieder, there is another active Jonathan again),
On Wed, 29 Nov 2017, Junio C Hamano wrote:
> * jn/reproducible-build (2017-11-22) 3 commits
> (merged to 'next' on 2017-11-27 at 6ae6946f8c)
> + Merge branch 'jn/reproducible-build' of ../git-gui into jn/reproducible-build
> + git-gui: sort entries in optimized tclIndex
> + generate-cmdlist: avoid non-deterministic output
>
> The build procedure has been taught to avoid some unnecessary
> instability in the build products.
I like this, from a purely security-informed point of view. Maybe there
would be a way to integrate this with the Continuous Testing we do? Like,
letting Travis verify that the binaries built from a certain Debian
package are really identical to the binaries built from the corresponding
commit? But I guess Travis is the wrong vehicle for this, as Travis needs
a *commit* to be pushed, not a new package to be made available via apt...
Ciao,
Dscho
next prev parent reply other threads:[~2017-12-01 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 1:17 What's cooking in git.git (Nov 2017, #08; Tue, 28) Junio C Hamano
2017-12-01 13:33 ` Johannes Schindelin
2017-12-01 13:38 ` cc/require-tcl-tk-for-build, was " Johannes Schindelin
2017-12-01 13:49 ` jt/diff-anchored-patience, " Johannes Schindelin
2017-12-01 13:56 ` Lars Schneider
2017-12-01 14:32 ` Johannes Schindelin [this message]
2017-12-01 15:41 ` jn/reproducible-build, was " Lars Schneider
2017-12-01 16:49 ` Jeff Hostetler
2017-12-03 0:27 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1.1712011526490.98586@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).