zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Zsh bugfixes released by RedHat
Date: Thu, 06 Nov 2014 08:30:35 -0800	[thread overview]
Message-ID: <141106083035.ZM3795@torch.brasslantern.com> (raw)
In-Reply-To: <545BAC56.1050804@eastlink.ca>

On Nov 6,  9:13am, Ray Andrews wrote:
}
} Do people ever tinker with zsh on any level above the personal and not
} coordinate it with you guys?  Wouldn't that end up creating quite a mess?

Some of the OS packagers will roll patches for things that break their
specific system tests into their pre-compiled packages without telling
us directly, yes.  Usually though it's some patch we've already done
that they're just backporting to an older version that they consider
stable.

} Shouldn't they at least offer a patch to you so that it might become
} official everywhere?  It seems both rude and irresponsible.

Technically they are supposed to offer the patch to us, although zsh's
license is not as clingy that way as the GNU license for example.  In
RedHat's case the patches are probably in the .src.rpm bundle and we
could download and extract them if we wanted, I'm just trying to avoid
going through that if someone else already knows what's going on.


  reply	other threads:[~2014-11-06 16:31 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 [this message]
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

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=141106083035.ZM3795@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).