From: Paul Eggert <eggert@cs.ucla.edu>
To: Werner LEMBERG <wl@gnu.org>, bug-gnulib@gnu.org
Subject: Re: inflexible non-recursive support
Date: Tue, 22 Jun 2021 12:06:22 -0700 [thread overview]
Message-ID: <806d4193-6c4a-c74a-f0b8-a96a7520ee1a@cs.ucla.edu> (raw)
In-Reply-To: <20210622.183326.255236285487180571.wl@gnu.org>
On 6/22/21 9:33 AM, Werner LEMBERG wrote:
> I suggest a patch as below (which needs further polishing to properly
> canonicalize the directory path, I guess).
Thanks for the suggestion. Could you spell out a little more what sort
of polishing would be needed there? (I'm not a regular user of this
feature....)
next prev parent reply other threads:[~2021-06-22 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 16:33 inflexible non-recursive support Werner LEMBERG
2021-06-22 19:06 ` Paul Eggert [this message]
2021-06-23 9:16 ` Werner LEMBERG
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=806d4193-6c4a-c74a-f0b8-a96a7520ee1a@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@gnu.org \
--cc=wl@gnu.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).