From: "Bart Schaefer" <schaefer@closedmail.com>
To: zsh-workers@sunsite.dk
Subject: Re: Bug in _path_files
Date: Sun, 11 May 2003 18:06:09 +0000 [thread overview]
Message-ID: <1030511180609.ZM4013@candle.brasslantern.com> (raw)
In-Reply-To: <24777.1052388394@csr.com>
On May 8, 11:06am, Peter Stephenson wrote:
}
} Whoops, it seems the old fudge was documented and used in various
} places.
Dang. I grep'd for that the day you posted the patch, thinking it was
probably going to break something, but forgot to hit all the completion
subdirectories ...
} Not quite sure what to do about 4.0 --- I applied the first patch but
} maybe it's better to leave it and document the bug.
There was a time I'd have said that was the way to go ... but now we have
assorted Linux distributions and the like bundling the "stable" releases,
so the longer we leave these kinds of discrepancies the worse the damage
is likely to be when 4.2 or 5.0 or whatever it will be, comes out.
So I'd recommend that you apply both patches to the 4.0 branch, and that
we (you) think about doing a 4.0.7 sometime soon.
next prev parent reply other threads:[~2003-05-11 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 19:14 Vin Shelton
2003-05-08 10:06 ` Peter Stephenson
2003-05-11 18:06 ` Bart Schaefer [this message]
2003-05-12 11:11 ` 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=1030511180609.ZM4013@candle.brasslantern.com \
--to=schaefer@closedmail.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).