zsh-users
 help / color / mirror / code / Atom feed
From: TJ Luoma <luomat@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh MailingList <zsh-users@zsh.org>
Subject: Re: Call for volunteers: Patch Manager
Date: Mon, 15 Feb 2021 16:06:42 -0500	[thread overview]
Message-ID: <CADjGqHuuaeP1Q_T70cf_xvSpUD288b_pkRE9_FjunuGgOEpjLw@mail.gmail.com> (raw)
In-Reply-To: <20210215202119.GA4949@tarpaulin.shahaf.local2>

[-- Attachment #1: Type: text/plain, Size: 689 bytes --]

On Mon, Feb 15, 2021 at 3:21 PM Daniel Shahaf <d.s@daniel.shahaf.name>
wrote:

> You needn't be a zsh developer yourself; you just need to be able to
follow a patch thread, and have
> time once a week or so to review a few such threads and reply with short
reminders where needed.

By "follow a patch thread" do you mean:

1. Read emails related to a topic and see that the conversation has stopped
or slowed, but no resolution (closed or merged) has occurred.

or

2. Be able to understand what a patch does and why it is important?


I think I could do the former. I could not do the latter.

~ Tj
(not officially volunteering just yet, but wanting to understand what the
'job' entails)

[-- Attachment #2: Type: text/html, Size: 1462 bytes --]

  reply	other threads:[~2021-02-15 21:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 20:21 Daniel Shahaf
2021-02-15 21:06 ` TJ Luoma [this message]
2021-02-15 22:20   ` Daniel Shahaf
2021-02-15 23:29     ` Ray Andrews
2021-02-17 22:36       ` Daniel Shahaf
2021-02-17 23:30         ` Ray Andrews
2021-02-18  1:42           ` TJ Luoma
2021-02-18 17:28             ` Daniel Shahaf
2021-02-18 23:16             ` Lawrence Velázquez
2021-02-22 16:39             ` Interactive menu completion bug Paul
2021-02-22 21:50               ` Bart Schaefer
2021-02-18 23:11         ` Call for volunteers: Patch Manager Lawrence Velázquez
2021-02-19 16:04           ` Daniel Shahaf

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=CADjGqHuuaeP1Q_T70cf_xvSpUD288b_pkRE9_FjunuGgOEpjLw@mail.gmail.com \
    --to=luomat@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --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).