From: Vitaly Zdanevich <zdanevich.vitaly@ya.ru>
To: gentoo-user@lists.gentoo.org, Michael <confabulate@kintzios.com>
Subject: Re: [gentoo-user] Emails are no indexable
Date: Tue, 9 Jul 2024 14:03:38 +0400 [thread overview]
Message-ID: <72c521ff-f60a-4bef-971d-9bf70ea8df29@ya.ru> (raw)
In-Reply-To: <2945403.e9J7NaK4W3@lenovo>
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
In https://marc.info/robots.txt I see
User-agent: *
Disallow: /
It looks bad.
On 7/8/24 21:41, Michael wrote:
> On Monday, 8 July 2024 16:07:59 BST Vitaly Zdanevich wrote:
>> Hi, I tried to google in "exact match" a few sentences from this email
>> list - and nothing found. For example this mirroring
>> https://marc.info/?l=gentoo-user&m=171984189706185&w=2 - and nothing in
>> Google. Is it excluded from search? This is bad, because people google
>> problems that are already solved in these emails :(
>>
>> Is it a known issue?
> It depends what Google or other web crawlers have decided to list in their
> search results and what to exclude. You should be able to run a search within
> the content of a single website, but only if it has been ranked/listed by
> Google, e.g. say you want to find posts about blurred fonts, in a gentoo M/L,
> but not Debian, contained in marc.info. You can search Google like so:
>
> "blurred fonts" +gentoo -debian site:marc.info
>
> This should include Gentoo M/L posts about blurred fonts found in the
> marc.info domain, but exclude any Debian related search results.
> Unfortunately, this relies on Google first ranking them in their results to
> allow you to see them.
[-- Attachment #2: Type: text/html, Size: 1977 bytes --]
next prev parent reply other threads:[~2024-07-09 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 15:07 [gentoo-user] Emails are no indexable Vitaly Zdanevich
2024-07-08 15:10 ` Vitaly Zdanevich
2024-07-08 17:41 ` Michael
2024-07-09 10:03 ` Vitaly Zdanevich [this message]
2024-07-23 23:52 ` Hank Leininger
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=72c521ff-f60a-4bef-971d-9bf70ea8df29@ya.ru \
--to=zdanevich.vitaly@ya.ru \
--cc=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.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