From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org
Cc: virtio@lists.oasis-open.org, Paul Knight <paul.knight@oasis-open.org>
Subject: [virtio-comment] Re: [virtio-dev] [PATCH] changelog editorial fixes
Date: Tue, 10 May 2022 10:17:36 +0200 [thread overview]
Message-ID: <87ee113iov.fsf@redhat.com> (raw)
In-Reply-To: <20220510052929.69133-1-mst@redhat.com>
On Tue, May 10 2022, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> Paul Knight reports:
>
> Minor broken links in the "Revision History" - Appendix D
> - https://lists.oasis-open.org/archives/virtio-dev/201910/msg00057.html. (bad
> link due to inclusion of the terminating period - second item dated 01 Sep 2020
> in Appendix D Revision history) - not a blocking issue
> - https://lkml.org/lkml/2020/4/21/1020) (bad link due to including the final
> right parenthesis in the hyperlink - item dated 01 Sep 2020 by Petre Eftime) -
> not a blocking issue
These two are obvious formatting issues, which we may try to catch in
post-processing going forward.
> - https://github.org/oasis-tcs/virtio-spec/issues/97 (bad link due to using
> github.org instead of github.com - first item dated 30 Mar 2021 in Appendix D
> Revision history) - not a blocking issue
That error was pre-existing in the commit message the changelog had been
generated from -- we can fix it here (we can't fix it in the git
history); going forward, should we always try to fixup links for the
changelog? I imagine that links may end up in history that break later on.
>
> Reported-by: Paul Knight <paul.knight@oasis-open.org>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
> cl-os.tex | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Anyway,
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
prev parent reply other threads:[~2022-05-10 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 5:29 [virtio-dev] [PATCH] changelog editorial fixes Michael S. Tsirkin
2022-05-10 8:17 ` Cornelia Huck [this message]
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=87ee113iov.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=paul.knight@oasis-open.org \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.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 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.