zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: 3 years of coding Zsh
Date: Mon, 18 Jun 2018 16:00:21 +0100	[thread overview]
Message-ID: <20180618150024eucas1p15c206df2ce9b8b709bcd2359fe7637ec~5STEs8H4B0903809038eucas1p1j@eucas1p1.samsung.com> (raw)
In-Reply-To: <CAKc7PVAAAh9heU2rthfwk1Ptm9xxRkGTWLBeNfrPdP3wr+rwZg@mail.gmail.com>

On Sun, 17 Jun 2018 16:43:14 +0200
Sebastian Gniazdowski <sgniazdowski@gmail.com> wrote:
> I just felt that doing 7-8.5 commits per day not excluding holidays
> for 2 years and counting 3rd, and at this occasion verifying dark
> (undebugged) areas of Zsh code, what results in precious bug-fixes
> (like solid sched) is enough justification to ask.

The problem with that is none of the core zsh developers have
ever asked for contributions in a quarter century of its existence,
and all are unpaid volunteers.   So this does look a bit of hijack of
the list. In general, asking for contributions for a project of your
own is fine, of course.

So it would be appreciated if you could keep this to your own channels,
not the zsh ones.

Thanks.
pws


  reply	other threads:[~2018-06-18 15:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 16:55 Sebastian Gniazdowski
2018-06-15 17:29 ` Ray Andrews
2018-06-15 22:49   ` Jason L Tibbitts III
2018-06-17 12:41   ` Sebastian Gniazdowski
2018-06-17 14:21     ` Daniel Shahaf
2018-06-17 14:43       ` Sebastian Gniazdowski
2018-06-18 15:00         ` Peter Stephenson [this message]
2018-06-19  7:34           ` Sebastian Gniazdowski
2018-06-19  8:27             ` Peter Stephenson
2018-06-19  9:12           ` about founding z developement of zsh Marc Chantreux
2018-06-20 10:19             ` René Wilhelm
2018-06-20 11:02               ` Marc Chantreux
2018-06-21 21:44             ` Sebastian Gniazdowski
2018-06-17 17:39       ` 3 years of coding Zsh 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='20180618150024eucas1p15c206df2ce9b8b709bcd2359fe7637ec~5STEs8H4B0903809038eucas1p1j@eucas1p1.samsung.com' \
    --to=p.stephenson@samsung.com \
    --cc=zsh-users@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).