unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 5/5] gnu: Add khard.
Date: Sun, 13 Mar 2016 18:45:00 -0400	[thread overview]
Message-ID: <20160313224500.GA30947@jasmine> (raw)
In-Reply-To: <87ziu2rou5.fsf@gnu.org>

On Sun, Mar 13, 2016 at 11:32:34PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> 
> > * gnu/packages/mail.scm (khard): New variable.
> 
> [...]
> 
> > +    (home-page "https://github.com/scheibler/khard")
> > +    (license gpl3))) ; "later version" never mentioned
> 
> If the source file headers or other documents do not specify a version,
> then we write it as ‘gpl3+’ (in fact, Section 14 of GPLv3 says: “If the
> Program does not specify a version number of the GNU General Public
> License, you may choose any version ever published by the Free Software
> Foundation.”)

Okay, thanks for clarifying this. I've made the change. In this case,
the source files have no license headers. There is only the LICENSE
file.

> 
> > On Thu, Mar 03, 2016 at 05:11:56PM -0500, Leo Famulari wrote:
> >> * gnu/packages/mail.scm (khard): New variable.
> >> +    (description "Khard is an address book for the console.  It creates, reads,
> >> +modifies and removes CardDAV address book entries at your local machine.  For
> >> +synchronizing with a remote address book, @command{vdirsyncer} is recommended.
> >> +Khard can also be used from within the email client @command{mutt}.")
> >
> > Is this an appropriate use of texinfo?
> 
> Yes.
> 
> Thanks for your work, and sorry again for the delay!
> 
> Ludo’.

  reply	other threads:[~2016-03-13 22:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 22:11 [PATCH 0/5] Add Khard and dependencies Leo Famulari
2016-03-03 22:11 ` [PATCH 1/5] gnu: Add python2-atomicwrites Leo Famulari
2016-03-13 22:26   ` Ludovic Courtès
2016-03-03 22:11 ` [PATCH 2/5] gnu: python2-pyicu: Update to 1.9.2 Leo Famulari
2016-03-13 22:27   ` Ludovic Courtès
2016-03-03 22:11 ` [PATCH 3/5] gnu: Split python2-pyicu into python-pyicu and python2-pyicu Leo Famulari
2016-03-05 19:42   ` Efraim Flashner
2016-03-05 22:32     ` Leo Famulari
2016-03-06  0:40       ` Leo Famulari
2016-03-06 12:58       ` Andreas Enge
2016-03-06 18:49         ` Leo Famulari
2016-03-13 22:31           ` Leo Famulari
2016-03-13 22:28   ` Ludovic Courtès
2016-03-13 22:32     ` Leo Famulari
2016-03-03 22:11 ` [PATCH 4/5] gnu: Add python-vobject Leo Famulari
2016-03-13 22:28   ` Ludovic Courtès
2016-03-03 22:11 ` [PATCH 5/5] gnu: Add khard Leo Famulari
2016-03-03 22:14   ` Leo Famulari
2016-03-05 19:42   ` Efraim Flashner
2016-03-05 22:10     ` Leo Famulari
2016-03-13 22:32   ` Ludovic Courtès
2016-03-13 22:45     ` Leo Famulari [this message]
2016-03-05 19:42 ` [PATCH 0/5] Add Khard and dependencies Efraim Flashner
2016-03-05 22:11   ` 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=20160313224500.GA30947@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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).