From: "Vadim A. Misbakh-Soloviov" <gentoo@mva.name>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Need GitHub snapshot hash verification failure samples
Date: Thu, 06 Jul 2017 05:30:43 +0700 [thread overview]
Message-ID: <8150245.8Hq3EIxABr@note> (raw)
In-Reply-To: <1499284092.1134.1.camel@gentoo.org>
By the way, that is "known issue" on github (I already discussed that with
their support even few years ago). The answer was kinda "well, it can happen
time to time, since we can upgrade software like tar and/or git on some or all
of our servers and we never declared tarballs checksums similarity".
So, even if somebody will trigger that once more, I doub't github support will
answer something different this time.
next prev parent reply other threads:[~2017-07-05 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 19:48 [gentoo-dev] Need GitHub snapshot hash verification failure samples Michał Górny
2017-07-05 22:30 ` Vadim A. Misbakh-Soloviov [this message]
2017-07-08 22:09 ` William L. Thomson Jr.
2017-07-06 20:15 ` Sergei Trofimovich
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=8150245.8Hq3EIxABr@note \
--to=gentoo@mva.name \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox