From: John Darrington <john@darrington.wattle.id.au>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org, John Darrington <jmd@gnu.org>
Subject: Re: [PATCH] gnu: Add microcom
Date: Tue, 13 Sep 2016 19:37:49 +0200 [thread overview]
Message-ID: <20160913173749.GA25835@jocasta.intra> (raw)
In-Reply-To: <20160913153617.GA13516@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
On Tue, Sep 13, 2016 at 11:36:17AM -0400, Leo Famulari wrote:
On Sun, Sep 11, 2016 at 06:56:58PM +0200, John Darrington wrote:
> * gnu/packages/microcom.scm: New file.
> * gnu/local.mk (GNU_SYSTEM_MODULES): Add it.
> + (version "2016.01.09")
I think we should use the upstream tag, "v2016.01.0".
> + (source (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "git://git.pengutronix.de/git/tools/microcom.git")
> + (commit "caf3687611ca855b4fa80c2a9a2fbb020834fc4e")))
Then, you can use the tag name as the commit. The tag I mentioned is
equivalent to this commit.
I will do that. Thanks.
> + (license gpl2+)))
My interpretation of the first paragraph of COPYING [0] is that the
package is licensed under the GPL version 2 only. What do you think?
All the .c files in the package explicitly say "either version 2 of the License,
or (at your option) any later version".
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-09-13 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 16:56 [PATCH] gnu: Add microcom John Darrington
2016-09-13 15:36 ` Leo Famulari
2016-09-13 17:37 ` John Darrington [this message]
2016-09-13 17:50 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160913173749.GA25835@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=guix-devel@gnu.org \
--cc=jmd@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).