From nobody Mon Feb 9 01:06:30 2026 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) client-ip=170.10.129.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1650630320; cv=none; d=zohomail.com; s=zohoarc; b=Ho+sVYwdcJ8nSo60wG3yqzaRQhf52paVmdW9r+t5AOnSAtyn1SHPhd729EvJAavhZ9Sk42jKYdUIouFgbiQL4BIws9KundnpR8gU+6tRuMb+g0Nx2N79yuIa7Onf21FLZvbnpZvxw47QSvLwn1gin74+3EmiLdaNjtsw2eXd0Fw= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1650630320; h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=8XF1BvSzrPTZm742N2m9KGvUXV1D/vGGYTo4faywPBM=; b=PjzIGLB+yq+y6+W546Z1jtROM61iXUIiozbsfuKbXNE3TjKaeTKc9moK7BhJaUwP0HxBB6Dimz6XdUiWQrbqp1DMxg9v8WfizaFPGS/bsYBrkS9HLOI3oYMriJoj6bAji5Mf3TXlpCFlAtpmhueSDolbnND3xAaGSrZ0ZJys8/w= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.zohomail.com with SMTPS id 1650630320375127.76916971346918; Fri, 22 Apr 2022 05:25:20 -0700 (PDT) Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-142-cEbDVj3pN1eQo4ejaXwejw-1; Fri, 22 Apr 2022 08:23:50 -0400 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E92C080352D; Fri, 22 Apr 2022 12:23:47 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id D468815230A2; Fri, 22 Apr 2022 12:23:47 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 8E4361940354; Fri, 22 Apr 2022 12:23:47 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id B6E2C194034C for ; Fri, 22 Apr 2022 12:23:45 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 89EBF416362; Fri, 22 Apr 2022 12:23:45 +0000 (UTC) Received: from speedmetal.lan (unknown [10.40.208.36]) by smtp.corp.redhat.com (Postfix) with ESMTP id 0D54B416171 for ; Fri, 22 Apr 2022 12:23:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1650630319; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=8XF1BvSzrPTZm742N2m9KGvUXV1D/vGGYTo4faywPBM=; b=PQeYQZZq1r8RkUl34bLSURR03AiiqJ1sMTSRBYQRTrcOSTlPwa/Wdd2Zrc4bSGuglbKZYK YyI7mGiP6m1hj9WL7DyYSL/eGbb0gUmgP67/st1H9EkN/45ft6gZQZ2zWw45Z5YA/5TVxz lKqPtrdT96hCLKJmJ3qk718lisqBFco= X-MC-Unique: cEbDVj3pN1eQo4ejaXwejw-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Peter Krempa To: libvir-list@redhat.com Subject: [PATCH 13/15] docs: contact: Remove HTML anchors and adjust documents using them Date: Fri, 22 Apr 2022 14:23:29 +0200 Message-Id: In-Reply-To: References: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10 X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 2.85 on 10.11.54.7 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=libvir-list-bounces@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1650630322295100001 Content-Type: text/plain; charset="utf-8" Modify the name of the 'IRC discussion' paragraph to just 'IRC' so that the links keep working and remove the raw HTML anchors. Adjustment is needed for documents which were using the '#email' anchor which has now become '#mailing-lists'. Signed-off-by: Peter Krempa --- docs/contact.rst | 11 ++--------- docs/contribute.rst | 10 +++++----- docs/page.xsl | 2 +- docs/securityprocess.rst | 4 ++-- 4 files changed, 10 insertions(+), 17 deletions(-) diff --git a/docs/contact.rst b/docs/contact.rst index 75b1239301..19e1b66a52 100644 --- a/docs/contact.rst +++ b/docs/contact.rst @@ -1,6 +1,3 @@ -.. role:: anchor(raw) - :format: html - =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Contacting the project contributors =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D @@ -17,8 +14,6 @@ issues `__ that should be used inst= ead. So if your issue has security implications, ignore the rest of this page and follow the `se= curity process `__ instead. -:anchor:`` - Mailing lists ------------- @@ -78,10 +73,8 @@ discussion. Wherever possible, please generate the patch= es by using regarding developing libvirt and/or contributing is available on our `Contributor Guidelines `__ page. -:anchor:`` - -IRC discussion --------------- +IRC +--- Some of the libvirt developers may be found on IRC on the `OFTC IRC `__ network. Use the settings: diff --git a/docs/contribute.rst b/docs/contribute.rst index c95c8b59d2..6ed5426b8a 100644 --- a/docs/contribute.rst +++ b/docs/contribute.rst @@ -67,7 +67,7 @@ to libvirt. If you have ideas for other contributions fee= l free to follow them. have, or run into trouble with managing an existing deployment. While s= ome users may be able to contact a software vendor to obtain support, it is common to rely on community help forums such as `libvirt users mailing - list `__, or sites such as + list `__, or sites such as `stackoverflow. `__ People who are familiar with libvirt and have ability & desire to help = other users are encouraged to participate in these help forums. @@ -82,10 +82,10 @@ for communication between contributors: Mailing lists ~~~~~~~~~~~~~ -The project has a number of `mailing lists `__ for gen= eral -communication between contributors. In general any design discussions and = review -of contributions will take place on the mailing lists, so it is important = for -all contributors to follow the traffic. +The project has a number of `mailing lists `__= for +general communication between contributors. In general any design discussi= ons +and review of contributions will take place on the mailing lists, so it is +important for all contributors to follow the traffic. Instant messaging / chat ~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/docs/page.xsl b/docs/page.xsl index 7d0203cf62..0a0b017482 100644 --- a/docs/page.xsl +++ b/docs/page.xsl @@ -172,7 +172,7 @@ diff --git a/docs/securityprocess.rst b/docs/securityprocess.rst index fe64e94f80..23f7a39e96 100644 --- a/docs/securityprocess.rst +++ b/docs/securityprocess.rst @@ -35,8 +35,8 @@ format in the `libvirt-security-notice GIT repository `__ and `published online `__ in text, HTML and XML formats. Security notices are published on the `libvirt-announce mailing -list `__ when any embargo is lifte= d, or -as soon as triaged if already public knowledge. +list `__ when any embargo = is +lifted, or as soon as triaged if already public knowledge. Security team ------------- --=20 2.35.1