From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: New package: google-chrome-unstable
Date: Sat, 28 Dec 2019 00:29:30 +0100 [thread overview]
Message-ID: <20191227232930.d_YST2VpzmxCoM1wDtiV_0qxhfe6YB5etbMX12e3tA0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17824@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 464 bytes --]
New comment by rwt3k on void-packages repository
https://github.com/void-linux/void-packages/pull/17824#issuecomment-569363459
Comment:
> Do anyone knows what license should I use for the package? I just edited the google-chrome package by forking the master repository. So, it's the same license that's been used. Couldn't see any "chrome" or "freeware" license types in the travis license.lst.
There is no need to change. The same error occurs with Chrome.
next prev parent reply other threads:[~2019-12-27 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 21:50 [PR PATCH] Add google-chrome-unstable to srcpkgs voidlinux-github
2019-12-27 22:10 ` New package: google-chrome-unstable voidlinux-github
2019-12-27 23:29 ` voidlinux-github [this message]
2019-12-29 3:35 ` voidlinux-github
2019-12-29 3:35 ` [PR PATCH] [Closed]: " voidlinux-github
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=20191227232930.d_YST2VpzmxCoM1wDtiV_0qxhfe6YB5etbMX12e3tA0@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).