From nobody Fri May 17 06:07:30 2024 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=1655897928; cv=none; d=zohomail.com; s=zohoarc; b=H9j610lp01IPaNt4QB9CdXapxGUCOiIYOo8bJH+6C5J88BzBfXQ2khfiQZYSBb8GLcqB96slxRu6WLD2XRFtMbuoL5I2v3nTvB2R9ttxZlSbAo/W0aklS+JR5qbhpy3kqkRkuLuKty60RqmU1gk3GMNmfWt02CZdpsJTfL1est4= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1655897928; h=Content-Type:Content-Transfer-Encoding:Date:From:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:Sender:Subject:To; bh=S5kV8y/jVzBegteJZfUpSZyg23pav2kclDgSpx4vjyM=; b=kNHJ8bTPx66cpcLt4dC7y5GCvw8/PklUnkehRi9/Y+TzArFjJu7R/YUnOAYwgmQIm1sQii0wmHtMPLjy0GhnaqMOOgi+/cb2yKH210rmaRbCl26SQqYoGBWhLxBj73UE0xBem+8mu+OABw77UPRWlGoOkXMUStF08vj49pi1xfo= 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 1655897928988714.8432734539565; Wed, 22 Jun 2022 04:38:48 -0700 (PDT) Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-595-bpppnPPhNuSgElBSqFWKPw-1; Wed, 22 Jun 2022 07:38:44 -0400 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 322D338005CF; Wed, 22 Jun 2022 11:38:42 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (unknown [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id C5F92492CA4; Wed, 22 Jun 2022 11:38:41 +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 A0670194704C; Wed, 22 Jun 2022 11:38:41 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 06D7A194704A for ; Wed, 22 Jun 2022 11:38:40 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id D08DB2166B2A; Wed, 22 Jun 2022 11:38:39 +0000 (UTC) Received: from hjs.redhat.com (unknown [10.43.2.85]) by smtp.corp.redhat.com (Postfix) with ESMTP id 78F802166B29 for ; Wed, 22 Jun 2022 11:38:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1655897927; 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:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=S5kV8y/jVzBegteJZfUpSZyg23pav2kclDgSpx4vjyM=; b=XPQG5W2iYn6lYyjeTqq9vgMyOxzP2L2w3doTOinp6fbLDe+7y2XqfaZkeoTzEiJy/I7IN5 f6mDa/tQ2GeupA7mLpnWqd3g2nBL4gsYMe9siXdP3LX6Nc2rSr+1w9ca9Yu80gI616hin3 JT7ycqO82ElYYK170mNrp5penstTx0s= X-MC-Unique: bpppnPPhNuSgElBSqFWKPw-1 X-Original-To: libvir-list@listman.corp.redhat.com From: =?UTF-8?q?J=C3=A1n=20Tomko?= To: libvir-list@redhat.com Subject: [libvirt PATCH] docs: update links to listman Date: Wed, 22 Jun 2022 13:38:37 +0200 Message-Id: MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 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.9 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-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1655897930306100001 The mailman for mailing lists hosted by Red Hat seems to have moved to listman.redhat.com. While the old links still seem to work, point our docs to the new location to avoid the redirect. Signed-off-by: J=C3=A1n Tomko Reviewed-by: Michal Privoznik --- docs/bindings.rst | 2 +- docs/contact.rst | 12 ++++++------ docs/submitting-patches.rst | 2 +- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/bindings.rst b/docs/bindings.rst index 81a4a67067..522d443d50 100644 --- a/docs/bindings.rst +++ b/docs/bindings.rst @@ -57,6 +57,6 @@ For information on using libvirt on **Windows** `please s= ee the Windows support page `__. =20 Support, requests or help for libvirt bindings are welcome on the -`mailing list `__, +`mailing list `_= _, as usual try to provide enough background information and make sure you use recent version, see the `help page `__. diff --git a/docs/contact.rst b/docs/contact.rst index f8f7e806b3..f20801e895 100644 --- a/docs/contact.rst +++ b/docs/contact.rst @@ -21,9 +21,9 @@ There are three mailing-lists: =20 **libvir-list@redhat.com** (for development) Archives - https://www.redhat.com/archives/libvir-list + https://listman.redhat.com/archives/libvir-list List info - https://www.redhat.com/mailman/listinfo/libvir-list + https://listman.redhat.com/mailman/listinfo/libvir-list =20 This is a high volume mailing list. It is a place for discussions about= the **development** of libvirt. @@ -37,9 +37,9 @@ There are three mailing-lists: =20 **libvirt-users@redhat.com** (for users) Archives - https://www.redhat.com/archives/libvirt-users + https://listman.redhat.com/archives/libvirt-users List info - https://www.redhat.com/mailman/listinfo/libvirt-users + https://listman.redhat.com/mailman/listinfo/libvirt-users =20 This is a moderate volume mailing list. It is a place for discussions involving libvirt **users**. @@ -53,9 +53,9 @@ There are three mailing-lists: =20 **libvirt-announce@redhat.com** (for release notices) Archives - https://www.redhat.com/archives/libvirt-announce + https://listman.redhat.com/archives/libvirt-announce List info - https://www.redhat.com/mailman/listinfo/libvirt-announce + https://listman.redhat.com/mailman/listinfo/libvirt-announce =20 This is a low volume mailing list, with restricted posting, for announc= ements of new libvirt releases. diff --git a/docs/submitting-patches.rst b/docs/submitting-patches.rst index 7cb5c2e172..7bc22323ee 100644 --- a/docs/submitting-patches.rst +++ b/docs/submitting-patches.rst @@ -68,7 +68,7 @@ particularly bad at this. =20 If everything went well, your patch should show up on the `libvir-list -archives `__ in a +archives `__ in a matter of minutes; if you still can't find it on there after an hour or so, you should double-check your setup. **Note that, if you are not already a subscriber, your very first post to the --=20 2.34.1