From: Wayne Davison <wayned@users.sourceforge.net>
To: Zsh Workers <zsh-workers@sunsite.dk>
Subject: Re: Forgetting the 4.0-patch branch
Date: Wed, 17 Apr 2002 01:52:10 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.33L2.0204170130530.8844-100000@phong.blorf.net> (raw)
In-Reply-To: <1020416161206.ZM10242@candle.brasslantern.com>
Speaking of which, a few of my recent fixes should really go onto the
patch branch. Shall I get some approval first? I'd particularly like
to apply the anti-truncation fixes in 16890 and users/4678, the unposted
HISTSIZE-can't-go-below-2 fix, and possibly the latter half of 16703
(which made the "history" command better in boundary conditions).
..wayne..
next prev parent reply other threads:[~2002-04-17 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-16 14:34 Sven's patches (16990, 16991, and users/4836) Bart Schaefer
2002-04-16 14:54 ` Sven Wischnowsky
2002-04-16 16:12 ` Bart Schaefer
2002-04-17 8:52 ` Wayne Davison [this message]
2002-04-17 9:30 ` Forgetting the 4.0-patch branch 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=Pine.LNX.4.33L2.0204170130530.8844-100000@phong.blorf.net \
--to=wayned@users.sourceforge.net \
--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).