Re: [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-04-15 Thread Carl Worth
On Tue, 06 Apr 2010 19:01:07 +0200, Michal Sojka wrote: > here is my report of git's test-lib relicensing. The following is the > last list sent to me by Junio. I guess you have this information > somewhere in your mailbox as well. Hi Michal, Thanks for following up with this. > There are three

[PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-04-15 Thread Carl Worth
On Tue, 06 Apr 2010 19:01:07 +0200, Michal Sojka wrote: > here is my report of git's test-lib relicensing. The following is the > last list sent to me by Junio. I guess you have this information > somewhere in your mailbox as well. Hi Michal, Thanks for following up with this. > There are three

[PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-04-06 Thread Michal Sojka
On Sat, 20 Feb 2010, Carl Worth wrote: > This file has had no explicit license information noted in it, but > has clearly been created and modified according to the terms of GPLv2 > as with the rest of the git code base. > > The purpose of relicensing is to allow other GPLv3+ projects (in > partic

Re: [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-04-06 Thread Michal Sojka
On Sat, 20 Feb 2010, Carl Worth wrote: > This file has had no explicit license information noted in it, but > has clearly been created and modified according to the terms of GPLv2 > as with the rest of the git code base. > > The purpose of relicensing is to allow other GPLv3+ projects (in > partic

[notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-23 Thread Tay Ray Chuan
Hi, On Tue, Feb 23, 2010 at 11:42 AM, Junio C Hamano wrote: > FWIW, I only said "_at least_ you need consent from them", and it was not > meant to be an exhaustive list. ?"blame -C -C -C" may tell you more. Without substantial analysis, "blame" alone is not sufficient - it does not show which wo

Re: [notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-23 Thread Matthieu Moy
Junio C Hamano writes: >> http://thread.gmane.org/gmane.mail.notmuch.general/1389/focus=140156 [...] >> Meanwhile, a message ID lives forever and can be used in multiple >> contexts. > > Oh, I never said "do not use message ID". I said "message ID alone is not > good enough for most people". F

Re: [notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-23 Thread Carl Worth
On Mon, 22 Feb 2010 19:42:30 -0800, Junio C Hamano wrote: > Please drop the above the next time. Oops. Yes, I missed that. > FWIW, I only said "_at least_ you need consent from them", and it was not > meant to be an exhaustive list. "blame -C -C -C" may tell you more. Fair enough. > You are t

[notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-23 Thread Carl Worth
On Mon, 22 Feb 2010 19:42:30 -0800, Junio C Hamano wrote: > Please drop the above the next time. Oops. Yes, I missed that. > FWIW, I only said "_at least_ you need consent from them", and it was not > meant to be an exhaustive list. "blame -C -C -C" may tell you more. Fair enough. > You are t

[notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-23 Thread Johannes Schindelin
Hi, On Tue, 23 Feb 2010, Tay Ray Chuan wrote: > On Tue, Feb 23, 2010 at 11:42 AM, Junio C Hamano > wrote: > > FWIW, I only said "_at least_ you need consent from them", and it was > > not meant to be an exhaustive list. ?"blame -C -C -C" may tell you > > more. > > Without substantial analysi

[notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-23 Thread Matthieu Moy
Junio C Hamano writes: >> http://thread.gmane.org/gmane.mail.notmuch.general/1389/focus=140156 [...] >> Meanwhile, a message ID lives forever and can be used in multiple >> contexts. > > Oh, I never said "do not use message ID". I said "message ID alone is not > good enough for most people". F

Re: [notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-23 Thread Johannes Schindelin
Hi, On Tue, 23 Feb 2010, Tay Ray Chuan wrote: > On Tue, Feb 23, 2010 at 11:42 AM, Junio C Hamano > wrote: > > FWIW, I only said "_at least_ you need consent from them", and it was > > not meant to be an exhaustive list.  "blame -C -C -C" may tell you > > more. > > Without substantial analysi

Re: [notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-22 Thread Tay Ray Chuan
Hi, On Tue, Feb 23, 2010 at 11:42 AM, Junio C Hamano wrote: > FWIW, I only said "_at least_ you need consent from them", and it was not > meant to be an exhaustive list.  "blame -C -C -C" may tell you more. Without substantial analysis, "blame" alone is not sufficient - it does not show which wo

Re: [notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-22 Thread Junio C Hamano
Carl Worth writes: > From 8693995fde71e8b028318e1e83bdbb6ae759335a Mon Sep 17 00:00:00 2001 > From: Carl Worth > Date: Sat, 20 Feb 2010 11:41:24 -0800 > Subject: [PATCH] test-lib.sh: Add explicit license detail, with change from > GPLv2 to GPLv2+. Please drop the above the ne

[notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-22 Thread Junio C Hamano
Carl Worth writes: > From 8693995fde71e8b028318e1e83bdbb6ae759335a Mon Sep 17 00:00:00 2001 > From: Carl Worth > Date: Sat, 20 Feb 2010 11:41:24 -0800 > Subject: [PATCH] test-lib.sh: Add explicit license detail, with change from > GPLv2 to GPLv2+. Please drop the above the ne

Re: [notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-22 Thread Tay Ray Chuan
Hi, On Sun, Feb 21, 2010 at 3:55 AM, Carl Worth wrote: > The request for relicensing was presented to the git community in: > >        Message-ID: <871vgmki4f@steelpick.localdomain> > > and explicitly agreed to by Junio C Hamano, Sverre Rabbelier, Johannes > Schindelin, Pierre Habouzit, and J

Re: [notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-22 Thread Carl Worth
From 8693995fde71e8b028318e1e83bdbb6ae759335a Mon Sep 17 00:00:00 2001 From: Carl Worth Date: Sat, 20 Feb 2010 11:41:24 -0800 Subject: [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+. This file has had no explicit license information noted in it, but has

[notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-22 Thread Carl Worth

[notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-21 Thread Tay Ray Chuan
Hi, On Sun, Feb 21, 2010 at 3:55 AM, Carl Worth wrote: > The request for relicensing was presented to the git community in: > > ? ? ? ?Message-ID: <871vgmki4f.fsf at steelpick.localdomain> > > and explicitly agreed to by Junio C Hamano, Sverre Rabbelier, Johannes > Schindelin, Pierre Habouzit, an

[notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-20 Thread Johannes Schindelin
Hi, On Sat, 20 Feb 2010, Carl Worth wrote: > This file has had no explicit license information noted in it, but > has clearly been created and modified according to the terms of GPLv2 > as with the rest of the git code base. > > The purpose of relicensing is to allow other GPLv3+ projects (in >

Re: [notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-20 Thread Johannes Schindelin
Hi, On Sat, 20 Feb 2010, Carl Worth wrote: > This file has had no explicit license information noted in it, but > has clearly been created and modified according to the terms of GPLv2 > as with the rest of the git code base. > > The purpose of relicensing is to allow other GPLv3+ projects (in >

Re: [notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-20 Thread Junio C Hamano
Carl Worth writes: > This file has had no explicit license information noted in it, but > has clearly been created and modified according to the terms of GPLv2 > as with the rest of the git code base. > > The purpose of relicensing is to allow other GPLv3+ projects (in > particular, the notmuch p

[notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-20 Thread Junio C Hamano
Carl Worth writes: > This file has had no explicit license information noted in it, but > has clearly been created and modified according to the terms of GPLv2 > as with the rest of the git code base. > > The purpose of relicensing is to allow other GPLv3+ projects (in > particular, the notmuch p

[notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-20 Thread Carl Worth
This file has had no explicit license information noted in it, but has clearly been created and modified according to the terms of GPLv2 as with the rest of the git code base. The purpose of relicensing is to allow other GPLv3+ projects (in particular, the notmuch project: http://notmuchmail.org)

[notmuch] [PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-20 Thread Carl Worth
This file has had no explicit license information noted in it, but has clearly been created and modified according to the terms of GPLv2 as with the rest of the git code base. The purpose of relicensing is to allow other GPLv3+ projects (in particular, the notmuch project: http://notmuchmail.org)

[PATCH] test-lib.sh: Add explicit license detail, with change from GPLv2 to GPLv2+.

2010-02-20 Thread Carl Worth
This file has had no explicit license information noted in it, but has clearly been created and modified according to the terms of GPLv2 as with the rest of the git code base. The purpose of relicensing is to allow other GPLv3+ projects (in particular, the notmuch project: http://notmuchmail.org)