From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] lxc: fix hash of patch
Date: Mon, 29 May 2017 18:43:48 +0200 [thread overview]
Message-ID: <4nvtvdxcra.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: CAPi7W83jQ9Z2t9TDLc5ZRo1tmPHF4SkYD86aBAKkOD0=99zwnQ@mail.gmail.com
Am Mon, 29 May 2017 13:03:35 +0200 schrieb Fabrice Fontaine:
> Dear Thomas,
>
> 2017-05-29 12:12 GMT+02:00 Thomas Petazzoni <
> thomas.petazzoni at free-electrons.com>:
>
>> Hello,
>>
>> On Mon, 29 May 2017 09:48:12 +0200, Fabrice Fontaine wrote:
>> > Fix hash of bc5b27d6f6d166d2a6df47982cbe36041ce6b73.patch
>> >
>> > Signed-off-by: Fabrice Fontaine
>> > <fontaine.fabrice@gmail.com>
>>
>> Why did the hash changed?
>>
> I don't know, Bernd sent me an email about it so I fixed it. I don't
> think I made a mistake in my first patch because I had to delete my
> local patch file in dl repository to reproduce the issue. Can the hash
> on a github commit change? Should I download
> 7e0ed7ffa0438a3d0e200a881f2166dc3632dcda (merge commit) instead of
> bc5b27d6f6d166d2a6df47982cbe36041ce6b73?
Hi,
afaics there are two more hashes wrong for github patches:
In package/jack2/jack2.hash
ff1ed2c4524095055140370c1008a2d9cccc5645.patch
In package/qt/qt.hash the hash is wrong for
b8f98d956501dfa4ce03a137f15d404930a56066.patch
Regards, Bernd
next prev parent reply other threads:[~2017-05-29 16:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 7:48 [Buildroot] [PATCH/next 1/1] lxc: fix hash of patch Fabrice Fontaine
2017-05-29 10:12 ` Thomas Petazzoni
2017-05-29 11:03 ` Fabrice Fontaine
2017-05-29 16:43 ` Bernd Kuhls [this message]
2017-05-29 19:52 ` Thomas Petazzoni
2017-05-31 19:53 ` Thomas Petazzoni
2017-05-31 19:53 ` Thomas Petazzoni
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=4nvtvdxcra.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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