[libvirt PATCH 2/4] docs: update docs pointing to old mailing list addrs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Signed-off-by: Daniel P. Berrangé <berrange@xxxxxxxxxx>
---
 README.rst                  |  4 ++--
 docs/bindings.rst           |  2 +-
 docs/contact.rst            | 18 +++++++++---------
 docs/downloads.rst          |  2 +-
 docs/newreposetup.rst       |  2 +-
 docs/securityprocess.rst    |  2 +-
 docs/submitting-patches.rst | 10 +++++-----
 docs/testapi.rst            |  4 ++--
 8 files changed, 22 insertions(+), 22 deletions(-)

diff --git a/README.rst b/README.rst
index daabe76477..a2bcbd80ce 100644
--- a/README.rst
+++ b/README.rst
@@ -64,8 +64,8 @@ Contact
 
 The libvirt project has two primary mailing lists:
 
-* libvirt-users@xxxxxxxxxx (**for user discussions**)
-* libvir-list@xxxxxxxxxx (**for development only**)
+* users@xxxxxxxxxxxxxxxxx (**for user discussions**)
+* devel@xxxxxxxxxxxxxxxxx (**for development only**)
 
 Further details on contacting the project are available on the website:
 
diff --git a/docs/bindings.rst b/docs/bindings.rst
index 9991012bf9..3309f169c5 100644
--- a/docs/bindings.rst
+++ b/docs/bindings.rst
@@ -58,6 +58,6 @@ For information on using libvirt on **Windows** `please see the Windows
 support page <windows.html>`__.
 
 Support, requests or help for libvirt bindings are welcome on the
-`mailing list <https://listman.redhat.com/mailman/listinfo/libvir-list/>`__,
+`devel mailing list <https://lists.libvirt.org/admin/lists/devel.lists.libvirt.org/>`__,
 as usual try to provide enough background information and make sure you
 use recent version, see the `help page <bugs.html>`__.
diff --git a/docs/contact.rst b/docs/contact.rst
index f20801e895..a88f91fa71 100644
--- a/docs/contact.rst
+++ b/docs/contact.rst
@@ -19,11 +19,11 @@ Mailing lists
 
 There are three mailing-lists:
 
-**libvir-list@xxxxxxxxxx** (for development)
+**devel@xxxxxxxxxxxxxxxxx** (for development)
    Archives
-     https://listman.redhat.com/archives/libvir-list
+     https://lists.libvirt.org/archives/list/devel@xxxxxxxxxxxxxxxxx/
    List info
-     https://listman.redhat.com/mailman/listinfo/libvir-list
+     https://lists.libvirt.org/admin/lists/devel.lists.libvirt.org/
 
    This is a high volume mailing list. It is a place for discussions about the
    **development** of libvirt.
@@ -35,11 +35,11 @@ There are three mailing-lists:
    -  Development of language bindings for libvirt API
    -  Testing and documentation of libvirt
 
-**libvirt-users@xxxxxxxxxx** (for users)
+**users@xxxxxxxxxxxxxxxxx** (for users)
    Archives
-     https://listman.redhat.com/archives/libvirt-users
+     https://lists.libvirt.org/archives/list/users@xxxxxxxxxxxxxxxxx/
    List info
-     https://listman.redhat.com/mailman/listinfo/libvirt-users
+     https://lists.libvirt.org/admin/lists/users.lists.libvirt.org/
 
    This is a moderate volume mailing list. It is a place for discussions
    involving libvirt **users**.
@@ -51,11 +51,11 @@ There are three mailing-lists:
    -  Development of applications on top of / using the libvirt API(s)
    -  Any other topics along these lines
 
-**libvirt-announce@xxxxxxxxxx** (for release notices)
+**announce@xxxxxxxxxxxxxxxxx** (for release notices)
    Archives
-     https://listman.redhat.com/archives/libvirt-announce
+     https://lists.libvirt.org/archives/list/announce@xxxxxxxxxxxxxxxxx/
    List info
-     https://listman.redhat.com/mailman/listinfo/libvirt-announce
+     https://lists.libvirt.org/admin/lists/announce.lists.libvirt.org/
 
    This is a low volume mailing list, with restricted posting, for announcements
    of new libvirt releases.
diff --git a/docs/downloads.rst b/docs/downloads.rst
index d3deec554d..00feb8a761 100644
--- a/docs/downloads.rst
+++ b/docs/downloads.rst
@@ -336,7 +336,7 @@ And there are also read-only mirrors on libvirt.org:
 
 Note that for most repositories, development happens via merge requests
 on GitLab. However, for the main `libvirt.git` repository all patch review and
-discussion only occurs on the `libvir-list <contact.html>`__ mailing list.
+discussion only occurs on the `devel <contact.html>`__ mailing list.
 
 The GitHub repository is read-only and pull requests and issues there are ignored.
 
diff --git a/docs/newreposetup.rst b/docs/newreposetup.rst
index ac2e6a15f1..d5375b23ea 100644
--- a/docs/newreposetup.rst
+++ b/docs/newreposetup.rst
@@ -41,7 +41,7 @@ required under the **Settings** page:
 
   * **Pipelines emails**
 
-    * *Recipients*: ``libvirt-ci@xxxxxxxxxx``
+    * *Recipients*: ``ci@xxxxxxxxxxxxxxxxx``
 
 * **Repository**
 
diff --git a/docs/securityprocess.rst b/docs/securityprocess.rst
index 23f7a39e96..1f5176ec75 100644
--- a/docs/securityprocess.rst
+++ b/docs/securityprocess.rst
@@ -20,7 +20,7 @@ address:
 
 ::
 
-   libvirt-security@xxxxxxxxxx
+   security@xxxxxxxxxxxxxxxxx
 
 NB. while this email address is backed by a mailing list, it is invitation only
 and moderated for non-members. As such you will receive an auto-reply indicating
diff --git a/docs/submitting-patches.rst b/docs/submitting-patches.rst
index 5b857f9111..a5e108550a 100644
--- a/docs/submitting-patches.rst
+++ b/docs/submitting-patches.rst
@@ -35,7 +35,7 @@ When you want to post your patches:
   $ git pull --rebase
   (fix any conflicts)
   $ git send-email --cover-letter --no-chain-reply-to --annotate \
-                   --confirm=always --to=libvir-list@xxxxxxxxxx master
+                   --confirm=always --to=devel@xxxxxxxxxxxxxxxxx master
 
 For a single patch you can omit ``--cover-letter``, but a
 series of two or more patches needs a cover letter.
@@ -51,13 +51,13 @@ to your SMTP server with something like:
 
   $ git config --global sendemail.smtpServer stmp.youremailprovider.net
 
-If you get tired of typing ``--to=libvir-list@xxxxxxxxxx`` all
+If you get tired of typing ``--to=devel@xxxxxxxxxxxxxxxxx`` all
 the time, you can configure that to be automatically handled as
 well:
 
 ::
 
-  $ git config sendemail.to libvir-list@xxxxxxxxxx
+  $ git config sendemail.to devel@xxxxxxxxxxxxxxxxx
 
 Avoid using mail clients for sending patches, as most of them
 will mangle the messages in some way, making them unusable for
@@ -65,8 +65,8 @@ our purposes. Gmail and other Web-based mail clients are
 particularly bad at this.
 
 If everything went well, your patch should show up on the
-`libvir-list
-archives <https://listman.redhat.com/archives/libvir-list/>`__ in a
+`devel list
+archives <https://lists.libvirt.org/archives/list/devel@xxxxxxxxxxxxxxxxx/>`__ 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
diff --git a/docs/testapi.rst b/docs/testapi.rst
index 5f02e2872f..e05732e019 100644
--- a/docs/testapi.rst
+++ b/docs/testapi.rst
@@ -30,5 +30,5 @@ For more details you can look at:
 
 Libvirt-test-API is maintained using `a GIT
 repository <https://gitlab.com/libvirt/libvirt-test-API>`__, and comment,
-patches and reviews are carried on the `libvir-list <contact.html>`__
-development list.
+patches and reviews are carried on the `devel <contact.html>`__
+mailing list.
-- 
2.41.0




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux