virtio-comment.lists.oasis-open.org archive mirror
 help / color / mirror / Atom feed
From: Chet Ensign <chet.ensign@oasis-open.org>
To: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Cc: virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] Expired certificate on https://docs.oasis-open.org/
Date: Tue, 5 Sep 2023 09:51:30 -0400	[thread overview]
Message-ID: <CAAwgnnNQXD+94ksPV21mSa58=HGiaUi1-E5YMG=BJHj21fjUOg@mail.gmail.com> (raw)
In-Reply-To: <CAAjaMXaJb+BgKj2_Ou0ghzu-HogMSdqLH=8RJrfFrTKj2dmoqg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

Thank you Manos. We are on that.

On Mon, Sep 4, 2023 at 2:05 AM Manos Pitsidianakis <
manos.pitsidianakis@linaro.org> wrote:

> oasis-open.org has a valid certificate, but docs.* does not.
>
> 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/
>
>

-- 
Chet Ensign

Chief Technical Community Steward

OASIS Open

+1 201-341-1393 <+1+201-341-1393>
chet.ensign@oasis-open.org
www.oasis-open.org

[-- Attachment #2: Type: text/html, Size: 5148 bytes --]

      reply	other threads:[~2023-09-05 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04  6:03 [virtio-comment] Expired certificate on https://docs.oasis-open.org/ Manos Pitsidianakis
2023-09-05 13:51 ` Chet Ensign [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='CAAwgnnNQXD+94ksPV21mSa58=HGiaUi1-E5YMG=BJHj21fjUOg@mail.gmail.com' \
    --to=chet.ensign@oasis-open.org \
    --cc=manos.pitsidianakis@linaro.org \
    --cc=virtio-comment@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).