From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/31548] New: Update local search
Date: Sun, 24 Mar 2024 23:55:48 +0000 [thread overview]
Message-ID: <bug-31548-14326@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31548
Bug ID: 31548
Summary: Update local search
Product: sourceware
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: Infrastructure
Assignee: overseers at sourceware dot org
Reporter: mark at klomp dot org
Target Milestone: ---
Both https://sourceware.org/ and https://gcc.gnu.org/ contain a local (web)
search form. Extended versions https://gcc.gnu.org/search.html and
https://sourceware.org/search.html
We are running mnogosearch to provide local search for. Since mnogosearch is
totally dead now (last release in 2015) we need a replacement.
When we do we should also look at giving it its own database.
It currently shares mysql with bugzilla and patchwork.
Also inbox.sourceware.org does provide fairly good search (based on xapian).
Maybe we can extend that?
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2024-03-24 23:55 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=bug-31548-14326@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.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).