zsh-workers
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-workers@zsh.org
Subject: Re: Zsh bugfixes released by RedHat
Date: Thu, 06 Nov 2014 13:57:24 -0800	[thread overview]
Message-ID: <545BEEC4.7030603@eastlink.ca> (raw)
In-Reply-To: <20141106201516.GL5405@sym.noone.org>

On 11/06/2014 12:15 PM, Axel Beckert wrote:
> } Shouldn't they at least offer a patch to you so that it might become
> } official everywhere?
> I know of nearly no license requiring that. And if so, at least Debian
> would consider such a license as non-free[1].
I wasn't considering it from the point of view of legal requirements, 
but just from the
point of view of good manners and sound practice.  Having various 
different editions of
zsh (or anything) floating around out there that may or may not be 
compatible seems
like a bad idea. (Strictly necessary 'local' compatibility issues for 
any given distro
being, as Bart said, an exception. )  I was just curious if that sort of 
thing happens
very often.  Seems to me very poor for Bart to stumble upon a RedHat 
supposed
bug fix that he doesn't even know about.  You might think they'd notify 
us. Just
wondering.


      parent reply	other threads:[~2014-11-06 20:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 15:56 Bart Schaefer
2014-11-06 16:58 ` Jérémie Roquet
2014-11-06 17:04 ` Christian Neukirchen
2014-11-06 18:40   ` Bart Schaefer
2014-11-06 17:13 ` Ray Andrews
2014-11-06 16:30   ` Bart Schaefer
2014-11-06 20:15     ` Axel Beckert
2014-11-06 20:47       ` Bart Schaefer
2014-11-06 22:10         ` Christian Neukirchen
2014-11-06 22:21           ` Jérémie Roquet
2014-11-07 15:06             ` Christian Neukirchen
2014-11-06 22:10         ` Axel Beckert
2014-11-06 21:57       ` Ray Andrews [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=545BEEC4.7030603@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --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).