From: Mark Wielaard <mark@klomp.org>
To: Tom Tromey <tom@tromey.com>
Cc: Lancelot SIX <lsix@lancelotsix.com>,
Luis Machado <luis.machado@arm.com>,
Simon Marchi <simark@simark.ca>,
"gdb@sourceware.org" <gdb@sourceware.org>,
John Baldwin <jhb@FreeBSD.org>
Subject: Re: Any concrete plans after the GDB BoF?
Date: Sat, 4 Feb 2023 12:36:56 +0100 [thread overview]
Message-ID: <20230204113656.GC3398@gnu.wildebeest.org> (raw)
In-Reply-To: <87cz6vhgsd.fsf@tromey.com>
Hi Tom,
On Mon, Jan 30, 2023 at 02:08:18PM -0700, Tom Tromey wrote:
> >>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:
>
> Mark> For gdb-patches you want to add the following to your .git/config:
>
> Mark> [b4]
> Mark> midmask = https://inbox.sourceware.org/gdb-patches/%s
> Mark> linkmask = https://inbox.sourceware.org.org/gdb-patches/%s
Note the typo in the second line. It has double org.org. Obviously
should be single .org.
> I also have:
>
> searchmask = https://inbox.sourceware.org/gdb-patches/all/?x=m&t=1&q=%s
>
> Do I not need this?
Interesting. This is a new setting for using a global search index on
the public-inbox instance. If we had that on inbox.sourceware.org the
URL would be: https://inbox.sourceware.org/all/?x=m&t=1&q=%s I am not
sure which functionality of b4 this matches to. It would help with
searches of references of a commit on other mailinglists.
If it is just for the gdb-patches list then the URL would be
https://inbox.sourceware.org/gdb-patches/?x=m&t=1&q=%s
Having a full global text search for all lists is slightly heavy (it
is a full text index by xapian. If you can figure out what it
precisely is used for then we have to see how much extra disk space is
needed for that.
If it is just for text searching of auxiliary lists then the following
might all that is needed:
https://inbox.sourceware.org/binutils/?x=m&t=1&q=%s
(aka, text search just the binutils list)
Cheers,
Mark
next prev parent reply other threads:[~2023-02-04 11:36 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 10:47 Luis Machado
2022-10-28 16:16 ` Simon Marchi
2022-10-28 16:51 ` John Baldwin
2022-10-28 16:54 ` Simon Marchi
2022-10-31 9:28 ` Luis Machado
2022-10-31 13:17 ` Simon Marchi
2022-10-31 13:37 ` Joel Brobecker
2022-10-31 14:15 ` Simon Marchi
2022-10-31 17:31 ` Joel Brobecker
2023-02-11 17:13 ` Andrew Burgess
2023-02-12 12:43 ` Mark Wielaard
2023-02-13 11:54 ` Andrew Burgess
2023-02-13 12:52 ` Luis Machado
2023-02-13 14:24 ` Tom Tromey
2023-02-13 14:42 ` Luis Machado
2023-02-13 15:13 ` Andrew Burgess
2023-02-13 15:23 ` Luis Machado
2023-02-14 5:48 ` Joel Brobecker
2023-02-15 14:47 ` Andrew Burgess
2023-02-16 4:14 ` Joel Brobecker
2023-02-16 9:51 ` Mark Wielaard
2023-02-16 10:16 ` Joel Brobecker
2023-02-16 11:58 ` Eli Zaretskii
2023-02-16 13:31 ` Joel Brobecker
2023-02-16 15:23 ` Eli Zaretskii
2023-02-14 13:07 ` Mark Wielaard
2023-02-14 14:23 ` Pedro Alves
2023-02-14 13:00 ` Mark Wielaard
2023-02-15 14:36 ` Andrew Burgess
2023-02-13 14:05 ` Tom Tromey
2022-12-15 10:17 ` Luis Machado
2023-01-01 22:02 ` Mark Wielaard
2023-01-20 17:30 ` Tom Tromey
2023-01-20 20:30 ` Tom Tromey
2023-01-27 15:50 ` Lancelot SIX
2023-01-27 23:50 ` Tom Tromey
2023-01-30 17:43 ` Lancelot SIX
2023-01-30 18:46 ` Mark Wielaard
2023-01-30 21:08 ` Tom Tromey
2023-02-04 11:36 ` Mark Wielaard [this message]
2023-01-31 10:00 ` Lancelot SIX
2022-12-13 2:48 ` Frank Ch. Eigler
2023-02-16 8:53 anix
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=20230204113656.GC3398@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=gdb@sourceware.org \
--cc=jhb@FreeBSD.org \
--cc=lsix@lancelotsix.com \
--cc=luis.machado@arm.com \
--cc=simark@simark.ca \
--cc=tom@tromey.com \
/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).