From: Jason McCarty <bclg@iup.edu>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: tla completion
Date: Tue, 16 Mar 2004 11:48:29 -0500 [thread overview]
Message-ID: <20040316164829.GA12838@iup.edu> (raw)
In-Reply-To: <20040312010950.GA2239@scowler.net>
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
Clint Adams wrote:
[RE my completion for tla]
> If you, Erik, and Rob want to assign copyright to Peter or the Zsh
> Development Group or whatever it is we do, we'll clean it up a bit and
> include it upstream.
OK, we're all willing to relicense under the ZSH license. Emails from
Rob and Erik are attached.
I also had the thought that you could get the options and their
descriptions (but not the syntax) from "tla $command -h", negating the
need to include the help text in the completion itself. But I don't know
when I might have time to implement such a thing.
Thanks for your interest,
Jason McCarty
[-- Attachment #2: Type: message/rfc822, Size: 1762 bytes --]
From: Erik Toubro Nielsen <erik@tntech.dk>
To: Jason McCarty <bclg@iup.edu>
Subject: Re: relicense tla completion for inclusion in zsh upstream?
Date: Fri, 12 Mar 2004 20:37:25 +0100
Message-ID: <m2ad2ldfgq.fsf@upstroke.mdsdenmark.com>
Hi Jason,
Jason McCarty <bclg@iup.edu> writes:
> Hi,
>
> I've gotten mail from Clint Adams <clint@zsh.org> that he'd like to
> clean up my zsh completion for tla and include it in zsh upstream. To do
> so, I think it needs to be relicensed under zsh's license
> (http://cvs.sourceforge.net/viewcvs.py/zsh/zsh/LICENCE?view=markup).
> Would you both be willing to relicense your contributions that way?
Yes I would.
Erik Toubro Nielsen
>
> Thanks.
>
> --
> Jason McCarty <bclg@iup.edu>
[-- Attachment #3: Type: message/rfc822, Size: 2793 bytes --]
[-- Attachment #3.1.1: Type: text/plain, Size: 745 bytes --]
On Thu, Mar 11, 2004 at 10:18:58PM -0500, Jason McCarty said
> Hi,
>
> I've gotten mail from Clint Adams <clint@zsh.org> that he'd like to
> clean up my zsh completion for tla and include it in zsh upstream. To do
> so, I think it needs to be relicensed under zsh's license
> (http://cvs.sourceforge.net/viewcvs.py/zsh/zsh/LICENCE?view=markup).
> Would you both be willing to relicense your contributions that way?
I'd be happy to:
I hearby offer my zsh tla completion work under the same license as zsh
itself, in addition to the GNU GPL, version 2 or later.
--
Rob Weir <rweir@ertius.org> | mlspam@ertius.org | Do I look like I want a CC?
Words of the day: Rule Psix Juiliett Class Submarine beanpole satellite imagery
[-- Attachment #3.1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-16 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 15:49 Clint Adams
2004-03-11 23:38 ` Jason McCarty
2004-03-12 0:11 ` Clint Adams
2004-03-12 0:26 ` Jason McCarty
2004-03-12 1:09 ` Clint Adams
2004-03-12 3:03 ` Jason McCarty
2004-03-12 10:23 ` Peter Stephenson
2004-03-16 16:48 ` Jason McCarty [this message]
2004-03-16 19:35 ` Clint Adams
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=20040316164829.GA12838@iup.edu \
--to=bclg@iup.edu \
--cc=zsh-workers@sunsite.dk \
/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.vuxu.org/mirror/zsh/
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).