From: Edesio Costa e Silva <edesio@softaplic.com.br>
To: barkalow@iabervon.org
Cc: Edesio Costa e Silva <edesio@task.com.br>, git@vger.kernel.org
Subject: Re: Approxidate licensing
Date: Tue, 10 Oct 2006 15:33:25 -0300 [thread overview]
Message-ID: <20061010183325.GC12993@softaplic.com.br> (raw)
In-Reply-To: <1073a5540610101128q3fb9f68fsf3a28fbda20927d1@mail.gmail.com>
Try the TCL modules that parse date and time (tclGetDate.y and
tclClock.c). They are licensed BSD style.
Edésio
> From: Daniel Barkalow <barkalow@iabervon.org>
> Date: Oct 10, 2006 2:39 PM
> Subject: Approxidate licensing
> To: Linus Torvalds <torvalds@osdl.org>, Junio C Hamano
> <junkio@cox.net>, dwmw2@infradead.org
> Cc: git@vger.kernel.org
>
>
> I'm working on an LGPL project (for my company; it's obscure enough and
> we're lazy enough that we're not really distributing it in general in
> either source or binary form), and I'm running into the usual date parsing
> issue (i.e., all the standard functions are broken in various ways). My
> plan has been to write my own, but it's hard to get the motivation when
> approxidate exists, works well, and is open source.
>
> Would the three of you agree to license date.c under the LGPL or BSD? It
> looks like you're the only authors of non-trivial changes [1]. And it seems
> reasonable to want the date parsing thing under non-GPL terms outside of
> git.
>
> -Daniel
> *This .sig left intentionally blank*
>
> [1] git log and git blame are pretty impressive, but they don't quite
> catch that most of date.c was written by David as part of commit-tree.c,
> then Tony replaced it with a version that uses curl, then Edgar separated
> it out into a date.c and simultaneously reverted Tony's changes. On the
> other hand, the commit messages do say this, and you can use git log and
> git blame to verify that they're true. The only thing they don't let
> you verify is what the differences are between the date.c added in
> ecee9d9e and the similar part of commit-tree.c in 812666c8. If someone
> wants to make git blame *really* magic, date.c would be a good test case.
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-10-10 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 17:39 Approxidate licensing Daniel Barkalow
2006-10-10 18:17 ` Linus Torvalds
[not found] ` <1073a5540610101128q3fb9f68fsf3a28fbda20927d1@mail.gmail.com>
2006-10-10 18:33 ` Edesio Costa e Silva [this message]
2006-10-10 19:23 ` Junio C Hamano
2006-10-10 20:54 ` Junio's wishes [Was: Re: Approxidate licensing] Horst H. von Brand
2006-10-10 22:12 ` Linus Torvalds
2006-10-11 7:55 ` Approxidate licensing Junio C Hamano
2006-10-11 7:57 ` David Woodhouse
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=20061010183325.GC12993@softaplic.com.br \
--to=edesio@softaplic.com.br \
--cc=barkalow@iabervon.org \
--cc=edesio@ieee.org \
--cc=edesio@task.com.br \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).