All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicolas Dechesne" <nicolas.dechesne@linaro.org>
To: Quentin Schulz <quentin.schulz@streamunlimited.com>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>,
	 Robert Berger <robert.berger@reliableembeddedsystems.com>
Subject: Re: [docs] broken links
Date: Thu, 7 Jan 2021 18:08:25 +0100	[thread overview]
Message-ID: <CAP71WjyK679c8hjEE53PVyi-_8vX5TS6umsXk+y2TGio8c30hQ@mail.gmail.com> (raw)
In-Reply-To: <20210107165951.aqx4maful2uhopzx@qschulz>

[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]

On Thu, Jan 7, 2021 at 5:59 PM Quentin Schulz <
quentin.schulz@streamunlimited.com> wrote:

> Hi Nicolas,
>
> On Thu, Jan 07, 2021 at 05:52:49PM +0100, Nicolas Dechesne wrote:
> > hey!
> >
> > Robert opened a bug for a broken link in the doc, see
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=14168
> >
> > This is a valid bug, a regression in
> > e1bcfe4d8 dev-manual: remove unused labels
> >
> > Unfortunately, it opens a can of worms... since it looks like the built
> in
> > linkcheck did not detect the broken links, and this is not the only
> broken
> > link.
> >
> > I ran an online link checker on
> > https://docs.yoctoproject.org/dev-manual/common-tasks.html, and it
> reported
> > the following errors with anchors.. they look like they are regression
> with
> > the commit above..
> >
>
> [...]
>
> It'd be nice to fix the linkcheck indeed.
>

hmm. could it be that linkcheck only checks for 'external' links?


>
> I have on my todolist to remove all anchor links to use refs instead but
> it's
> not fun work to do and it's time consuming. I can now probably "automate"
> all of this with some python regexp and manually fix the ones returned
> by your online link checker :) (and use the online link checker to
> validate the changes).
>
> I'd then add in the README/CONTRIBUTING that we do not allow such links
> and we have to be careful to enforce this when receiving patches.
>
> All this in the event that we can't find what's wrong with our
> linkcheck.
>
> Cheers,
> Quentin
>

[-- Attachment #2: Type: text/html, Size: 2416 bytes --]

  reply	other threads:[~2021-01-07 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 16:52 broken links Nicolas Dechesne
2021-01-07 16:59 ` [docs] " Quentin Schulz
2021-01-07 17:08   ` Nicolas Dechesne [this message]
2021-01-13 18:26     ` Nicolas Dechesne
2021-04-07 16:12       ` Quentin Schulz
2021-04-07 16:40         ` Nicolas Dechesne
2021-04-07 16:47           ` Quentin Schulz
2021-04-07 16:54             ` Nicolas Dechesne

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=CAP71WjyK679c8hjEE53PVyi-_8vX5TS6umsXk+y2TGio8c30hQ@mail.gmail.com \
    --to=nicolas.dechesne@linaro.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@streamunlimited.com \
    --cc=robert.berger@reliableembeddedsystems.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.