From: iotku <iotku@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: sublime-text4: update license_checksum
Date: Thu, 16 Jun 2022 22:35:52 +0200 [thread overview]
Message-ID: <20220616203552.dw3AvmkHTqLRBE8bdRKVuUStX5cr6OikWQFVDEEj320@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37586@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
There's a closed pull request on the void-packages repository
sublime-text4: update license_checksum
https://github.com/void-linux/void-packages/pull/37586
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
Previously, the build would fail as the checksum of the license has changed.
I'm not aware of any notice of changes to the text, so it's likely just a minor formatting change in the html which is being check-summed. Additionally, sublime-merge-bin (sublime-text's sister project) uses the same EULA and respective checksum as provided here.
next prev parent reply other threads:[~2022-06-16 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 18:21 [PR PATCH] " iotku
2022-06-16 20:27 ` iotku
2022-06-16 20:35 ` iotku [this message]
2022-06-16 20:43 [PR PATCH] " iotku
2022-06-18 23:34 ` [PR PATCH] [Closed]: " classabbyamp
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=20220616203552.dw3AvmkHTqLRBE8bdRKVuUStX5cr6OikWQFVDEEj320@z \
--to=iotku@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).