From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/2] lei - expanding relative paths for `lei up'
Date: Thu, 1 Dec 2022 11:21:30 +0000 [thread overview]
Message-ID: <20221201112132.4005900-1-e@80x24.org> (raw)
I ran `lei q --only ./ -o $MAILDIR $QUERY' at some point from
inside an inboxdir.
Then I got confused when `lei up --all' running from $HOME
started complaining about $HOME/objects being missing from ALE.
It turned out $HOME/public-inbox (one of my worktrees) was
causing $HOME to false-positive as a v1 public-inbox for lei :x.
So this is a two-pronged fix to prevent some weird stuff from
happening.
Eric Wong (2):
lei: stricter external checks for valid $GIT_DIR/objects
lei_saved_search: expand only/include/exclude to absolute paths
lib/PublicInbox/LeiQuery.pm | 23 ++++++++++++++++++++---
lib/PublicInbox/LeiXSearch.pm | 14 ++++++++++----
t/lei-q-save.t | 13 +++++++++----
t/lei.t | 3 ++-
4 files changed, 41 insertions(+), 12 deletions(-)
next reply other threads:[~2022-12-01 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 11:21 Eric Wong [this message]
2022-12-01 11:21 ` [PATCH 1/2] lei: stricter external checks for valid $GIT_DIR/objects Eric Wong
2022-12-01 11:21 ` [PATCH 2/2] lei_saved_search: expand only/include/exclude to absolute paths Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221201112132.4005900-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.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).