From: Lyndon Brown <jnqnfe@gmail.com>
To: git@vger.kernel.org
Subject: [gitk] searching misses relevant commits
Date: Mon, 31 Aug 2020 06:08:12 +0100 [thread overview]
Message-ID: <14a46bcf8da119af8b8882fe77a0d96ff3984b1a.camel@gmail.com> (raw)
Hi,
When searching commits (by which I mean the "find" feature), sometimes
relevant entries are missed which should have been selected. I reported
this to Debian as bug #969197 ([1]).
I gave an example in the Debian bug report of searching the VLC
codebase for commits adding/removing "set_capability" (exact; all
fields). While 888451fe5146a49de8d49e830dbe57dd478e358f was one of
those found, the adjacent
commit 46650ad3f7f92d2757c43b42aa170965dc1df25c was skipped, despite it
being entirely relevant.
Changing to IgnCase makes no difference.
I'm a Debian Linux user, running version 1:2.28.0-1.
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969197
reply other threads:[~2020-08-31 5:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=14a46bcf8da119af8b8882fe77a0d96ff3984b1a.camel@gmail.com \
--to=jnqnfe@gmail.com \
--cc=git@vger.kernel.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