From: ludo@gnu.org (Ludovic Courtès)
To: Marek Benc <merkur32@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add nvi
Date: Tue, 02 Sep 2014 21:36:34 +0200 [thread overview]
Message-ID: <87vbp5olvh.fsf@gnu.org> (raw)
In-Reply-To: <5405C55A.6050301@gmail.com> (Marek Benc's message of "Tue, 02 Sep 2014 15:25:46 +0200")
Marek Benc <merkur32@gmail.com> skribis:
> On 09/02/2014 02:29 PM, Ludovic Courtès wrote:
[...]
>> Could you send the patch (with the added comments) as an attachment,
>> because the mail client apparently mangled it?
>
> Okay, It's as an attachment. Here's the changelog entries:
>
> 2014-09-02 Marek Benc <merkur32@gmail.com>
> * gnu/packages/nvi.scm: New file.
> * gnu/packages/patches/nvi-assume-preserve-path.patch: New file.
> * gnu-system.am: Added the preceding 2 files.
Actually, if you make the 3 lines above part of the commit log, ‘git
format-patch’ will preserve them, and so the patch will be directly
applicable with ‘git am’–which is better. :-)
Anyway I’ve now pushed the patch, thanks!
[...]
> (The files in the clib/ subdirectory bear a BSD-4 license header, yet the
> only copyright holder of those files is the University of California,
> Berkeley, which removed the ad-clause in 1997 retroactively (i.e. it
> relicensed all BSD-4 code under its copyright to BSD-3). Thus those files
> are effectively distributed under the BSD-3 license as well.)
This seems to be the explanation: at some point UC Berkeley changed the
license to BSD-3, which it can do as the sole copyright holder.
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-09-02 19:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 13:33 [PATCH] Add nvi Marek Benc
2014-09-02 8:19 ` Ludovic Courtès
2014-09-02 9:58 ` Marek Benc
2014-09-02 12:29 ` Ludovic Courtès
2014-09-02 13:25 ` Marek Benc
2014-09-02 19:36 ` Ludovic Courtès [this message]
2014-09-02 10:09 ` Cyril Roelandt
2014-09-02 10:18 ` Taylan Ulrich Bayirli/Kammer
2014-09-02 12:21 ` Ludovic Courtès
2014-09-02 12:18 ` Ludovic Courtès
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=87vbp5olvh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=merkur32@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.