From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: 03/04: gnu: Add git-when-merged.
Date: Mon, 19 Nov 2018 22:20:25 +0100 [thread overview]
Message-ID: <87in0svk6e.fsf@gnu.org> (raw)
In-Reply-To: <87pnv4vy9z.fsf@netris.org> (Mark H. Weaver's message of "Sat, 17 Nov 2018 04:38:37 -0500")
Hi Mark,
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> civodul pushed a commit to branch master
>> in repository guix.
>>
>> commit 243bdcc12e40c8dbd1129fa5b613d8f247744f31
>> Author: Kyle Meyer <kyle@kyleam.com>
>> Date: Mon Nov 12 16:24:23 2018 -0500
>>
>> gnu: Add git-when-merged.
>>
>> * gnu/packages/version-control.scm (git-when-merged): New variable.
>>
>> Signed-off-by: Ludovic Courtès <ludo@gnu.org>
>> ---
>> gnu/packages/version-control.scm | 52 ++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 52 insertions(+)
>
> The license field of this package is incorrect. It has this:
>
> (license license:gpl2)
>
> which is understandable given that GitHub shows the license as "GPL-2.0"
> on the main project page <https://github.com/mhagger/git-when-merged>.
> However, if you look at the actual code, there's only one source file
> and it has a proper GNU GPLv2+ copyright notice at the top.
>
> https://github.com/mhagger/git-when-merged/blob/master/bin/git-when-merged
>
> The only other files in the repository are README.md and COPYING.
Indeed, my bad: knowing that Git is GPLv2-only, I took it for granted
that git-when-merged was licensed similarly.
I’ll push the fix shortly, thanks for the heads-up!
Ludo’.
prev parent reply other threads:[~2018-11-19 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181116221822.30957.35914@vcs0.savannah.gnu.org>
[not found] ` <20181116221823.7F00D209C2@vcs0.savannah.gnu.org>
2018-11-17 9:38 ` 03/04: gnu: Add git-when-merged Mark H Weaver
2018-11-17 16:07 ` Kyle Meyer
2018-11-19 21:20 ` Ludovic Courtès [this message]
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=87in0svk6e.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
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).