All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Quentin Schulz <foss@0leil.net>, docs@lists.yoctoproject.org
Cc: michael.opdenacker@bootlin.com
Subject: Re: [docs] [PATCH 1/1] Update documentation URL
Date: Mon, 22 Mar 2021 15:46:55 +0100	[thread overview]
Message-ID: <9aeeb509-7a46-a761-2782-7d28dc0199c0@bootlin.com> (raw)
In-Reply-To: <099D8738-5946-4A6B-8A31-C575E7B77F4E@0leil.net>

Hi Quentin,

Nice to hear from you again, and thanks for your help!

> Please use :yocto_docs: extlink here. IIRC, :yocto_docs:`/` should do just fine.


Oops, actually, this doesn't work here, as we are in a "code-block". The
patch didn't give you enough context for you to see this.

>
> You can find the list of our extlinks in documentation/conf.py. They can be used in rST files (so your change in README is fine).


This is very good to know, thanks!

Apparently, these shortcuts don't work in the toplevel index.rst file
though... That was tempting to use them there too. Anyway, I'll use them
in normal documentation.


>
>>       For more information about OpenEmbedded see their website:
>>           http://www.openembedded.org
> And a free patch here with :oe_home:`/` :)


Same here, unfortunately.

So, I believe my patch can be taken as is...

Cheers,

Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2021-03-22 14:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 18:13 [PATCH 0/1] Update documentation URL Michael Opdenacker
2021-03-19 18:13 ` [PATCH 1/1] " Michael Opdenacker
2021-03-20 11:16   ` [docs] " Quentin Schulz
2021-03-22 14:46     ` Michael Opdenacker [this message]
2021-03-23  9:27       ` Quentin Schulz
2021-03-31  9:22         ` Michael Opdenacker

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=9aeeb509-7a46-a761-2782-7d28dc0199c0@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=foss@0leil.net \
    /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.