From: Bart Schaefer <schaefer@brasslantern.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: "Lawrence Velázquez" <vq@larryv.me>,
"Zsh hackers list" <zsh-workers@zsh.org>
Subject: Re: Patch management workflow for threads that peter out (was: Re: [PATCH] Fix [:IDENT:] vs posixidentifiers)
Date: Sun, 28 Mar 2021 23:35:58 -0700 [thread overview]
Message-ID: <CAH+w=7aHfkd_xbNq+tMrth4=g41v0rOnXWhv1Y8b9hVtr7qE-A@mail.gmail.com> (raw)
In-Reply-To: <20210329063014.GK18178@tarpaulin.shahaf.local2>
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
On Sun, Mar 28, 2021, 11:30 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> That does bring up the point of what to do with threads that peter out
> without a review. I suggest that they be added to Etc/BUGS. WDYT?
>
Only if they actually are threads about bug fixes. Proposed new features
or completion improvements, just as examples, don't belong in the BUGS file.
>
[-- Attachment #2: Type: text/html, Size: 891 bytes --]
next prev parent reply other threads:[~2021-03-29 6:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 15:08 [PATCH] Fix [:IDENT:] vs posixidentifiers 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
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 [this message]
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='CAH+w=7aHfkd_xbNq+tMrth4=g41v0rOnXWhv1Y8b9hVtr7qE-A@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=d.s@daniel.shahaf.name \
--cc=vq@larryv.me \
--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).