zsh-users
 help / color / mirror / code / Atom feed
From: Richard Coleman <coleman@math.gatech.edu>
To: Robert Leslie <rob@advantage.org>
Cc: zsh-users@math.gatech.edu
Subject: Re: Zsh Copyright
Date: Thu, 14 Dec 1995 10:09:44 -0500	[thread overview]
Message-ID: <199512141509.KAA05542@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Thu, 14 Dec 1995 05:53:24 EST." <199512141053.FAA00511@abba.ccs.neu.edu>

> I am a zsh fan, although I'm not subscribed to this list so I'd appreciate a
> private response.
> 
> I have a question about the copyright status of Zsh, because I would like to
> redistribute a prepackaged version of the software in both source and binary
> form for the Debian/GNU Linux project. In order to be included, the software
> must be able to be freely modified and redistributed without restriction.
> Anyone must be able to make copies of it, modify it, redistribute it with
> their modifications in place, include it on a CD-ROM, or generally sell it.

I've have been given permission by the original copyright holder
to change the copyright of zsh to a Berkeley style copyright.
This change happened after the release of zsh-2.5.03, but
the beta releases for the next release contain this type of
copyright message.  I don't know the timetable for the Debian
group, but I would suggest either wait for the next release, or
use zsh-2.6-beta12 in their distribution (beta12 is already more
stable than the last production release).  There is precedent
for this, as the FreeBSD group uses zsh-2.6-beta10 in their
ports collection.

If you have any more questions about this, you can send them directly
to me.

Richard Coleman         (Coordinator, Zsh Development Group)
zsh@math.gatech.edu
coleman@math.gatech.edu


           reply	other threads:[~1995-12-14 15:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <199512141053.FAA00511@abba.ccs.neu.edu>]

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=199512141509.KAA05542@redwood.skiles.gatech.edu \
    --to=coleman@math.gatech.edu \
    --cc=rob@advantage.org \
    --cc=zsh-users@math.gatech.edu \
    /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).