zsh-workers
 help / color / mirror / code / Atom feed
From: "Lawrence Velázquez" <vq@larryv.me>
To: Stephane Chazelas <stephane@chazelas.org>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH] Fix [:IDENT:] vs posixidentifiers
Date: Mon, 22 Mar 2021 19:45:59 -0400	[thread overview]
Message-ID: <748AD4F6-A0D6-42D1-9E65-6C9028B8B69A@larryv.me> (raw)
In-Reply-To: <20210322171746.67pb332lvf3a3pkk@chazelas.org>

Hi Stephane,

> On Mar 22, 2021, at 1:17 PM, Stephane Chazelas <stephane@chazelas.org> wrote:
> 
> Maybe it would help to publish review queues on zsh.org (may as
> flat list of workers/1234 lines for each reviewer), so patch
> submitters can know whether or not the patch is being considered
> but reviewer are overwhelmed or it simply fell through the cracks.

My apologies, as patch manager I should have brought this to the
list's attention, but I haven't worked back past mid-February yet.

vq

  reply	other threads:[~2021-03-22 23:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 15:08 Stephane Chazelas
2021-02-07 15:50 ` Stephane Chazelas
2021-02-07 20:24   ` Bart Schaefer
2021-02-08  5:53     ` Daniel Shahaf
2021-02-08 20:51       ` Bart Schaefer
2021-02-09  9:11         ` Peter Stephenson
2021-03-22 17:17   ` Stephane Chazelas
2021-03-22 23:45     ` Lawrence Velázquez [this message]
2021-03-25  1:06       ` Daniel Shahaf
2021-03-28  1:48         ` Lawrence Velázquez
2021-03-29  6:30           ` Patch management workflow for threads that peter out (was: Re: [PATCH] Fix [:IDENT:] vs posixidentifiers) Daniel Shahaf
2021-03-29  6:35             ` Bart Schaefer
2021-03-29  7:26               ` Daniel Shahaf
2021-05-16 17:07                 ` Lawrence Velázquez
2021-05-16 18:24                   ` Bart Schaefer
2021-05-18  0:38                     ` Daniel Shahaf
2021-03-23  5:34     ` [PATCH] Fix [:IDENT:] vs posixidentifiers dana

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=748AD4F6-A0D6-42D1-9E65-6C9028B8B69A@larryv.me \
    --to=vq@larryv.me \
    --cc=stephane@chazelas.org \
    --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).