From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>,
mst@redhat.com, virtio-dev@lists.oasis-open.org
Cc: virtio-comment@lists.oasis-open.org, shahafs@nvidia.com,
Parav Pandit <parav@nvidia.com>
Subject: [virtio-dev] Re: [PATCH] changelog: Fix missing reference to driver notifications
Date: Thu, 16 Feb 2023 09:01:23 +0100 [thread overview]
Message-ID: <87ttzm9gz0.fsf@redhat.com> (raw)
In-Reply-To: <20230216053457.414126-1-parav@nvidia.com>
On Thu, Feb 16 2023, Parav Pandit <parav@nvidia.com> wrote:
> Cited commit in fixes tag missed to update the reference to drivers
> notifications section in past change log.
> Fix the reference.
>
> Fixes: be2ce1ee17e0 ("content.tex Fix Driver notifications label")
> Signed-off-by: Parav Pandit <parav@nvidia.com>
> ---
> cl-os.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Does it really make sense to patch the changelog? This is about the
1.1->1.2 changes, and I'd assume it is only relevant for the released
1.2 spec. We'll replace the changelog anyway when we do the 1.3 release.
[Speaking of the 1.3 release, we really should be planning for it. Maybe
target June or so, with a freeze in April?]
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-02-16 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 5:34 [PATCH] changelog: Fix missing reference to driver notifications Parav Pandit
2023-02-16 8:01 ` Cornelia Huck [this message]
2023-02-16 21:13 ` Parav Pandit
2023-02-16 23:42 ` [virtio-comment] " 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=87ttzm9gz0.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@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.