From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: Removing an inbox from extindex
Date: Mon, 30 Aug 2021 20:22:24 +0000 [thread overview]
Message-ID: <20210830202224.GA25528@dcvr> (raw)
In-Reply-To: <20210830201723.dehoul4y6gpqf2cp@nitro.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Mon, Aug 30, 2021 at 07:27:32PM +0000, Eric Wong wrote:
> > Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> > > Hello:
> > >
> > > What's the proper procedure to remove an inbox from extindex? For example, if
> > > I wanted to drop a source from being replicated to lore.kernel.org, how do I
> > > properly remove it from /all/ search results?
> >
> > public-inbox-extindex --gc $EXTINDEX_DIR
>
> This works, though there are some interesting side-effects to it. For example,
> I removed the /gitolite-transparency-log/* feed (it was too noisy and wasn't
> useful for anything, really). After running the --gc, I see lots of messages
> about things being removed, but /all/ still contains leftover entries from the
> inbox:
Yeah, it needs some work... I mostly forgot about it :x
(And somehow, I completely forgot about the existence of
syslog at some point :x)
next prev parent reply other threads:[~2021-08-30 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 19:17 Removing an inbox from extindex Konstantin Ryabitsev
2021-08-30 19:27 ` Eric Wong
2021-08-30 20:17 ` Konstantin Ryabitsev
2021-08-30 20:22 ` Eric Wong [this message]
2021-09-01 0:17 ` [PATCH] extindex: --gc removes messages from over, too 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=20210830202224.GA25528@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.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).