Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Angelo Compagnucci <angelo.compagnucci@gmail.com>
To: buildroot@buildroot.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Angelo Compagnucci <angelo.compagnucci@gmail.com>
Subject: [Buildroot] [PATCH 6/8] website/news: fix an unbalanced paragraph
Date: Wed,  4 Nov 2026 22:00:17 +0100	[thread overview]
Message-ID: <20261104210019.3509258-7-angelo.compagnucci@gmail.com> (raw)
In-Reply-To: <20261104210019.3509258-1-angelo.compagnucci@gmail.com>

In the "Moved to git" entry, a <pre> block is nested in a paragraph.
A <pre> can't be part of a paragraph, so the browser closes the
paragraph before it, and the </p> that follows is left unmatched.

Close the paragraph before the <pre> block, and put the following
sentence in its own paragraph.

Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
---
 docs/website/news.html | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/docs/website/news.html b/docs/website/news.html
index 2295abbf57..d7e680e41a 100644
--- a/docs/website/news.html
+++ b/docs/website/news.html
@@ -10153,10 +10153,9 @@
 	  to <a href="http://git-scm.org">Git</a>. You can browse the
 	  repo online
 	  <a href="http://git.buildroot.net/buildroot">here</a>, and clone
-	  the repo using:
-	  <pre>git clone git://git.buildroot.net/buildroot</pre>
-	  See the <a href="/git.html">Git Access</a> page for more details.
-	</p>
+	  the repo using:</p>
+	<pre>git clone git://git.buildroot.net/buildroot</pre>
+	<p>See the <a href="/git.html">Git Access</a> page for more details.</p>
       </div>
     </div>
   </li>
-- 
2.34.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2026-11-04 21:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 21:00 [Buildroot] [PATCH 0/8] website: follow-up fixes Angelo Compagnucci
2026-11-04 21:00 ` [Buildroot] [PATCH 1/8] website/download: make the table responsive Angelo Compagnucci
2026-11-04 21:00 ` [Buildroot] [PATCH 2/8] website: rework the navigation bar Angelo Compagnucci
2026-11-04 21:00 ` [Buildroot] [PATCH 3/8] website/index: align the hero on the grid Angelo Compagnucci
2026-11-04 21:00 ` [Buildroot] [PATCH 4/8] website: version the CSS and JS URLs Angelo Compagnucci
2026-11-04 21:00 ` [Buildroot] [PATCH 5/8] website/download: fix the git clone box on phones Angelo Compagnucci
2026-11-04 21:00 ` Angelo Compagnucci [this message]
2026-11-04 21:00 ` [Buildroot] [PATCH 7/8] website: escape the bare ampersands Angelo Compagnucci
2026-11-04 21:00 ` [Buildroot] [PATCH 8/8] DEVELOPERS: add Angelo Compagnucci for the website Angelo Compagnucci
2026-11-04 21:06 ` [Buildroot] [PATCH 0/8] website: follow-up fixes Thomas Petazzoni via buildroot

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=20261104210019.3509258-7-angelo.compagnucci@gmail.com \
    --to=angelo.compagnucci@gmail.com \
    --cc=buildroot@buildroot.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox