DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:sender:in-reply-to:references:date
	:x-google-sender-auth:message-id:subject:from:to:cc:content-type;
	b=V/zKB+IPf3lrkZv0MpBCR/Y0qQkF7JOR10fAHaH36MZnA5IOAOjwP/jWfUub09Kaes
	k03Q3qcqLsJosUzVqJWm/7O8bmbmNsJQtOaY8WI8WXA0g/KgUgQhAncInKV/uClq9zBW
	1jxUVZMNfLd/dT2mLP1nbkGWoopaqJbF+HMD4=
MIME-Version: 1.0
Sender: amdragon@gmail.com
In-Reply-To: <871v3vee7i.fsf@steelpick.2x.cz>
References: <1295783247-21900-1-git-send-email-sojkam1@fel.cvut.cz>
	<87fwscs63s.fsf@hermes.hocat.ca> <871v3vee7i.fsf@steelpick.2x.cz>
Date: Sat, 29 Jan 2011 14:13:25 -0500
Message-ID: <AANLkTinL-Lv2xxzbTd9k-b4YiQ7F8ZYrLP5Kv3_N_pJM@mail.gmail.com>
Subject: Re: [PATCH 0/4] Versatile date/time parser
From: Austin Clements <amdragon@mit.edu>
To: Michal Sojka <sojkam1@fel.cvut.cz>
Content-Type: text/plain; charset=ISO-8859-1
Cc: notmuch@notmuchmail.org
Precedence: list

What about CVS's getdate?  Is GPLv1 compatible?  As far as I can tell,
CVS's getdate depends only on yacc/bison and is probably
back-in-time-biased rather than forward-in-time-biased like the
coreutils getdate.

On Sat, Jan 29, 2011 at 1:50 PM, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
> On Sat, 29 Jan 2011, Tom Prince wrote:
>> On 2011-01-23, Michal Sojka wrote:
>> > Hi all,
>> >
>> > the following patch series brings into notmuch date/time parser stolen
>> > from GNU coreutils. It can be applied on top of custom query parser
>> > patches from Austin Clements.
>> >
>> > This is RFC and it not meant for merging.
>>
>> Another source for date parsing is perhaps date.c from git, which
>> (probably) has much smaller (none?) dependencies.
>
> Hmm, but Git is GPLv2 and notmuch is GPLv3 and these are not compatible.
>
> -Michal
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
>