From: Parav Pandit <parav@nvidia.com>
To: <virtio-comment@lists.linux.dev>, <mst@redhat.com>,
<cohuck@redhat.com>, <mvaralar@redhat.com>
Cc: <shahafs@nvidia.com>, Parav Pandit <parav@nvidia.com>
Subject: [PATCH 3/4] edit: Remove annotation of special character
Date: Mon, 27 Oct 2025 19:47:55 +0200 [thread overview]
Message-ID: <20251027174756.56284-4-parav@nvidia.com> (raw)
In-Reply-To: <20251027174756.56284-1-parav@nvidia.com>
PDF generation parsing complains when special character
annotation is listed in it. Remove such annotation in changelog.
Signed-off-by: Parav Pandit <parav@nvidia.com>
---
cl-os.tex | 7 -------
1 file changed, 7 deletions(-)
diff --git a/cl-os.tex b/cl-os.tex
index c5100f7..388a0ed 100644
--- a/cl-os.tex
+++ b/cl-os.tex
@@ -923,13 +923,6 @@
we started using implies that fixups are picked up
instead of the commit.
-For now, just switch to using regexp (dropping -F)
-and add "^" in front to only look for the string at
-beginning of the line.
-
-We'll worry about more elaborate logic later, if it's ever
-needed.
-
Message-Id: <1130700f4ae71a93d9887af35cf105731219f057.1721062136.git.mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
--
2.34.1
next prev parent reply other threads:[~2025-10-27 17:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 17:47 [PATCH 0/4] editorial: Prepare master branch for 1.4 spec release Parav Pandit
2025-10-27 17:47 ` [PATCH 1/4] edit: remove old changelog Parav Pandit
2025-10-27 17:47 ` [PATCH 2/4] edit: add changelog for 1.4 Parav Pandit
2025-10-27 17:47 ` Parav Pandit [this message]
2025-10-27 17:47 ` [PATCH 4/4] REVISION: update to 1.4 Parav Pandit
2025-10-27 17:56 ` [PATCH 0/4] editorial: Prepare master branch for 1.4 spec release Michael S. Tsirkin
2025-10-27 18:04 ` Parav Pandit
2025-10-27 18:06 ` Michael S. Tsirkin
2025-10-30 10:57 ` Parav Pandit
2025-10-27 18:08 ` Michael S. Tsirkin
2025-10-30 10:54 ` Parav Pandit
2025-10-30 10:59 ` Michael S. Tsirkin
2025-10-30 15:15 ` Parav Pandit
2025-11-06 15:42 ` Michael S. Tsirkin
2025-11-06 15:50 ` Michael S. Tsirkin
2025-10-27 18:05 ` Michael S. Tsirkin
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=20251027174756.56284-4-parav@nvidia.com \
--to=parav@nvidia.com \
--cc=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=mvaralar@redhat.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.linux.dev \
/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