From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/3] package/ca-certificates: don't hash certificates.crt
Date: Wed, 24 Oct 2018 14:32:32 +0200 [thread overview]
Message-ID: <8736sva5jz.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <baa8cebb-20a7-2dc2-a80b-c380721ff0ec@mind.be> (Arnout Vandecappelle's message of "Sun, 21 Oct 2018 14:38:14 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> Could you check if I'm correct, and if so, resubmit the series with:
>>
>> - the additional rm -f;
>> - a commit message that includes the explanation above;
>> - drops patch 2.
>>
>> If patch 2 really is needed, it needs a better explanation.
> ?Investigating a bit more turns out that I was rather wrong. The rm -f is
> already there, as correctly noted in your commit message. And patch 2 really is
> needed, it fixes a completely different set of duplicates.
> ?So I've extended the commit message a little and applied to master, thanks.
Committed to 2018.02.x and 2018.08.x with the extended commit message, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-10-24 12:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 22:05 [Buildroot] [PATCH v2 0/3] package/ca-certificates improvements Martin Bark
2018-06-16 22:05 ` [Buildroot] [PATCH v2 1/3] package/ca-certificates: don't hash certificates.crt Martin Bark
2018-06-17 19:25 ` Thomas Petazzoni
2018-06-18 9:51 ` Martin Bark
2018-06-18 14:39 ` Thomas Petazzoni
2018-06-21 22:04 ` Martin Bark
2018-10-21 13:15 ` Arnout Vandecappelle
2018-10-21 13:38 ` Arnout Vandecappelle
2018-10-21 14:03 ` Martin Bark
2018-10-24 12:32 ` Peter Korsgaard [this message]
2018-06-16 22:06 ` [Buildroot] [PATCH v2 2/3] package/ca-certificates: fix rebuilds Martin Bark
2018-06-16 22:06 ` [Buildroot] [PATCH v2 3/3] package/ca-certificates: create ca-certificates.crt reproducibly Martin Bark
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=8736sva5jz.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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