all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Roman Riabenko <roman@riabenko.com>
To: 54204@debbugs.gnu.org
Subject: bug#54204: mumi search by date provides unexpected results
Date: Tue, 01 Mar 2022 08:34:19 +0200	[thread overview]
Message-ID: <10b72780b0d916220e91d9ce3c59f4d8c6eaa2e7.camel@riabenko.com> (raw)

This report is for the instance at issues.guix.gnu.org. The hint under
the search field and the online help documentation suggest that "date:"
filter can be used to improve the search results.[1] However, the
results are different from what is documented. For example, there is a
report submitted on 16 February 2022 and a patch submitted on 20
Fenruary 2022 both contaning the word "mumi".[2][3] I can see them at
the end of search results when searching for "mumi".[4] But I cannot
find them with any of the following:

1. mumi date:20d..now
2. mumi date:2022-02-01..2022-02-28

The first one returns older posts only.[5] The second one returns
nothing.[6]

And the last hinted filter does return links to the expected issues but
also returns other issues which are apparently out of the specified
time period and so introduces noise in the search results making
filtering less effective:[7]

3. mumi date:1m..today

---

[1] https://issues.guix.gnu.org/help#search
[2] https://issues.guix.gnu.org/54024
[3] https://issues.guix.gnu.org/54072
[4] https://issues.guix.gnu.org/search?query=mumi
[5] https://issues.guix.gnu.org/search?query=mumi+date%3A20d..now
[6]
https://issues.guix.gnu.org/search?query=mumi+date%3A2022-02-01..2022-02-28
[7] https://issues.guix.gnu.org/search?query=mumi+date%3A1m..today

---

Roman





             reply	other threads:[~2022-03-01  6:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01  6:34 Roman Riabenko [this message]
2022-12-27 18:39 ` bug#54204: mumi search by date provides unexpected results kiasoc5 via Bug reports for GNU Guix
2024-05-10 20:53 ` Arun Isaac

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=10b72780b0d916220e91d9ce3c59f4d8c6eaa2e7.camel@riabenko.com \
    --to=roman@riabenko.com \
    --cc=54204@debbugs.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.