zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] Add openSUSE specific command completions
Date: Mon, 2 May 2011 12:48:10 +0100	[thread overview]
Message-ID: <20110502124810.332a421d@pws-pc.ntlworld.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1105012032210.28316@hp>

On Sun, 1 May 2011 20:40:07 -0400 (EDT)
"Benjamin R. Haskell" <zsh@benizi.com> wrote:
> On Sat, 30 Apr 2011, Peter Stephenson wrote:
> 
> > On Wed, 20 Apr 2011 15:49:43 +0200 İsmail Dönmez wrote:
> >> These completions were getting rot in openSUSE zsh package. It would 
> >> be nice to get them included upstream.
> >
> > Thanks, just got back from holiday, skipped with glazed eyes over 
> > zillions of emails but noticed this and committed it.
> 
> I noticed that a couple of those (_osc and _zypper) had copyright 
> notices in the files (which didn't seem to match the submitter), and 
> that they were "released under the GPLv2."
> 
> Are those okay to include without Zsh itself being GPL'ed?  I see the 
> LICENCE file states that "any provisions made in individual files take 
> precedence."  That makes it fine?

I'm not aware of it being a problem in shell functions, at least.
Typically it's after compilation where we need to be particularly
careful.  We already have GNU functions for configuration etc., although
that's a special case.

-- 
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/


      parent reply	other threads:[~2011-05-02 11:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 13:49 İsmail Dönmez
2011-04-26 12:09 ` İsmail Dönmez
2011-04-30 16:59 ` Peter Stephenson
2011-04-30 19:11   ` İsmail Dönmez
2011-05-02  0:40   ` Benjamin R. Haskell
2011-05-02  7:06     ` İsmail Dönmez
2011-05-02 11:48     ` Peter Stephenson [this message]

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=20110502124810.332a421d@pws-pc.ntlworld.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@zsh.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.
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).