You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by el...@apache.org on 2020/02/08 12:17:14 UTC

[maven-checkstyle-plugin] branch elharo-patch-1 created (now 82b89cd)

This is an automated email from the ASF dual-hosted git repository.

elharo pushed a change to branch elharo-patch-1
in repository https://gitbox.apache.org/repos/asf/maven-checkstyle-plugin.git.


      at 82b89cd  [MCHECKSTYLE-358] fix mailing list addres

This branch includes the following new commits:

     new 82b89cd  [MCHECKSTYLE-358] fix mailing list addres

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.



[maven-checkstyle-plugin] 01/01: [MCHECKSTYLE-358] fix mailing list addres

Posted by el...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

elharo pushed a commit to branch elharo-patch-1
in repository https://gitbox.apache.org/repos/asf/maven-checkstyle-plugin.git

commit 82b89cd2ac60a58532a232bf01c349d6cf1aa598
Author: Elliotte Rusty Harold <el...@users.noreply.github.com>
AuthorDate: Sat Feb 8 07:17:09 2020 -0500

    [MCHECKSTYLE-358] fix mailing list addres
    
    @khmarbaise
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 9b00120..6d129e0 100644
--- a/README.md
+++ b/README.md
@@ -35,7 +35,7 @@ Getting Started
 + Make sure you have a [JIRA account](https://issues.apache.org/jira/).
 + Make sure you have a [GitHub account](https://github.com/signup/free).
 + If you're planning to implement a new feature, it makes sense to discuss your changes 
-  on the [dev list](https://maven.apache.org/mail-lists.html) first. 
+  on the [dev list](https://maven.apache.org/mailing-lists.html) first. 
   This way you can make sure you're not wasting your time on something that isn't 
   considered to be in Apache Maven's scope.
 + Submit a ticket for your issue, assuming one does not already exist.