Github messages for voidlinux
 help / color / mirror / Atom feed
From: mobinmob <mobinmob@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sublime-merge: update to 2032.
Date: Thu, 03 Sep 2020 21:41:27 +0200	[thread overview]
Message-ID: <20200903194127.YmvrUVFhRrl6CMXITcgRqVjeyvSsf8iOBAjY29IHl0k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24620@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 568 bytes --]

New comment by mobinmob on void-packages repository

https://github.com/void-linux/void-packages/pull/24620#issuecomment-686716038

Comment:
> On 2020-09-02 13:45:27-0700, mobinmob ***@***.***> wrote: Sublime merge now installs under /opt.
> b. Distribution. You may not distribute or sell license keys or SUBLIME MERGE to third parties. Licenses will be revoked if distributed or sold to third parties. restricted=yes?

I am all for it, but users that have sublime-merge installed will stop getting updates from the repos. Is there a way to notify for the change?

  parent reply	other threads:[~2020-09-03 19:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02 20:45 [PR PATCH] " mobinmob
2020-09-03  0:09 ` [PR REVIEW] " ahesford
2020-09-03 12:49 ` sgn
2020-09-03 13:44 ` ahesford
2020-09-03 19:40 ` mobinmob
2020-09-03 19:41 ` mobinmob [this message]
2020-09-04 13:29 ` ahesford
2020-09-04 21:03 ` [PR PATCH] [Updated] " mobinmob
2020-09-04 21:06 ` mobinmob
2020-09-05  7:17 ` [PR REVIEW] " Chocimier
2020-09-05  9:54 ` mobinmob
2020-09-05 11:29 ` ahesford
2020-09-05 11:49 ` [PR REVIEW] " ahesford
2020-09-05 13:27 ` Chocimier
2020-09-05 13:32 ` Chocimier
2020-09-05 15:48 ` [PR PATCH] [Updated] " mobinmob
2020-09-05 15:55 ` mobinmob
2020-09-29  2:23 ` ericonr
2020-09-29  2:36 ` ahesford
2020-09-29 18:15 ` [PR PATCH] [Merged]: " Chocimier

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=20200903194127.YmvrUVFhRrl6CMXITcgRqVjeyvSsf8iOBAjY29IHl0k@z \
    --to=mobinmob@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).