All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <quentin.schulz@cherry.de>, <docs@lists.yoctoproject.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 1/8] conf.py: add linkcheck builder exclusions
Date: Wed, 15 Jul 2026 14:30:05 +0200	[thread overview]
Message-ID: <DJZ59GPEP45R.20F3GW82NNSF3@bootlin.com> (raw)
In-Reply-To: <a72acc48-890d-4a9e-8b22-5d02b5dee589@cherry.de>

Hi,

On Fri Jul 10, 2026 at 5:09 PM CEST, Quentin Schulz via lists.yoctoproject.org wrote:
> Hi Antonin,
>
> On 7/10/26 4:46 PM, Antonin Godard via lists.yoctoproject.org wrote:
>> The linkcheck builder can be used to scout for broken links. By looking at
>> the output of:
>> 
>>    grep -E -r --no-filename -o 'href="http.://[^/"]+' | sort | uniq -c | sort -nr
>> 
>> from the HTML output directory, exclude links that are too frequent.
>
> Because they are too frequent it's impossible they are broken? 
> Considering you fix links that are in this list later in this series, I 
> don't think this holds. At least provide a proper justification because 
> "too frequent" doesn't make sense.

I see your point. I did not want to hammer those websites, that is all. I'll
drop this patch I think. Maybe I could add this but commented out, in case
someone also wants to apply those exclusions.

Antonin


  reply	other threads:[~2026-07-15 12:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10 14:46 [PATCH 0/8] Fix broken links Antonin Godard
2026-07-10 14:46 ` [PATCH 1/8] conf.py: add linkcheck builder exclusions Antonin Godard
2026-07-10 15:09   ` [docs] " Quentin Schulz
2026-07-15 12:30     ` Antonin Godard [this message]
2026-07-10 14:46 ` [PATCH 2/8] conf.py: add extra links known to be broken Antonin Godard
2026-07-10 15:13   ` [docs] " Quentin Schulz
2026-07-15 12:30     ` Antonin Godard
2026-07-10 14:46 ` [PATCH 3/8] migration-guides/release-notes-3.4.2.rst: fix a broken link Antonin Godard
2026-07-10 14:46 ` [PATCH 4/8] docs-wide: fix broken path links Antonin Godard
2026-07-10 14:46 ` [PATCH 5/8] ref-manual/classes.rst: replace obsolete mailing list thread Antonin Godard
2026-07-10 14:46 ` [PATCH 6/8] ref-manual/images.rst: update obsolete VMWare links Antonin Godard
2026-07-10 14:46 ` [PATCH 7/8] migration-guides/release-notes-5.0.rst: remove broken link Antonin Godard
2026-07-10 14:46 ` [PATCH 8/8] docs-wide: fix various broken links Antonin Godard

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=DJZ59GPEP45R.20F3GW82NNSF3@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@cherry.de \
    --cc=thomas.petazzoni@bootlin.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 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.