From: "Jun. T" <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: [PATCH 1/2] Consolidated nofork substitution changes
Date: Sat, 23 Sep 2023 10:41:03 +0900 [thread overview]
Message-ID: <AA29D16B-6A6C-4C09-A25A-6724250A5F9B@kba.biglobe.ne.jp> (raw)
In-Reply-To: <CAH+w=7Y3VfxuZDfSF4O05nxLFRVyvoCBBZnW0dePGBQhKe2LbA@mail.gmail.com>
> 2023/09/23 9:25, Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> I think this.
The patch is somewhat mis-formatted?
(it can be easily applied manually).
So ztuff() is no longer necessary?
next prev parent reply other threads:[~2023-09-23 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-16 22:20 Bart Schaefer
2023-09-22 4:16 ` Jun T
2023-09-22 4:32 ` Jun T
2023-09-23 0:25 ` Bart Schaefer
2023-09-23 1:41 ` Jun. T [this message]
2023-09-23 2:01 ` Bart Schaefer
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=AA29D16B-6A6C-4C09-A25A-6724250A5F9B@kba.biglobe.ne.jp \
--to=takimoto-j@kba.biglobe.ne.jp \
--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).