From: Jonathan Corbet <corbet@lwn.net>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Documentation stragglers for 6.3
Date: Tue, 28 Feb 2023 15:47:03 -0700 [thread overview]
Message-ID: <87sfepwgpk.fsf@meer.lwn.net> (raw)
The following changes since commit cc29eadef921fe52aa58f32536a93d9ea0ca3eb7:
Documentation/watchdog/hpwdt: Fix Format (2023-02-16 17:31:29 -0700)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-6.3-2
for you to fetch changes up to 901578a45950bcc4d5055a24e9016d61b84dc1a2:
docs: recommend using Link: whenever using Reported-by: (2023-02-23 12:47:46 -0700)
----------------------------------------------------------------
A handful of documentation patches that were ready before the merge window,
but which I didn't get merged for the first round:
- A recommendation from Thorsten (also akpm) on use of Link tags to point
out problem reports.
- Some front-page formatting tweaks
- Another Spanish translation
- One typo(ish) fix.
----------------------------------------------------------------
Carlos Bilbao (1):
docs/sp_SP: Add process programming-language translation
Lukas Bulwahn (1):
docs: locking: refer to the actual existing config names
Randy Dunlap (1):
Documentation: front page: use recommended heading adornments
Thorsten Leemhuis (1):
docs: recommend using Link: whenever using Reported-by:
Documentation/index.rst | 17 +++----
Documentation/locking/locktorture.rst | 4 +-
Documentation/process/5.Posting.rst | 3 +-
Documentation/process/submitting-patches.rst | 9 ++--
Documentation/translations/sp_SP/process/index.rst | 1 +
.../sp_SP/process/programming-language.rst | 53 ++++++++++++++++++++++
6 files changed, 72 insertions(+), 15 deletions(-)
create mode 100644 Documentation/translations/sp_SP/process/programming-language.rst
next reply other threads:[~2023-02-28 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 22:47 Jonathan Corbet [this message]
2023-03-01 0:13 ` pr-tracker-bot
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=87sfepwgpk.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linuxfoundation.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
all inboxes | Powered by JetHome®