From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Is anyone able to take on zsh 4.2?
Date: Sat, 04 Nov 2006 10:13:30 -0800 [thread overview]
Message-ID: <061104101330.ZM15735@torch.brasslantern.com> (raw)
In-Reply-To: <200611021637.kA2GbrdM014352@news01.csr.com>
On Nov 2, 4:37pm, Peter Stephenson wrote:
}
} Porting patches to the 4.2 branch of zsh has been rather lax [...]
}
} Does anyone have time to do this?
Ordinarily I'd volunteer to do this, but circumstances have conspired
to limit my available time. I might have a chance to do some catch-
up over the Thanksgiving holiday in a few weeks, but I don't want to
make promises I might not keep.
next prev parent reply other threads:[~2006-11-04 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 16:37 Peter Stephenson
2006-11-04 18:13 ` Bart Schaefer [this message]
2006-11-16 3:00 ` arno.
2006-11-16 10:33 ` Peter Stephenson
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=061104101330.ZM15735@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/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).