aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2015-06-22 08:52:11 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2015-06-22 13:40:20 +0200
commit3f5563877a493a3a2060659ebe4b7aae62a17d84 (patch)
treeac134d31ffa8ffa5acf0da793e45fd2d6de93b94 /README.md
parentbe6420407b37c4c45a42874ea3cd974605fb65dc (diff)
downloadbitcoin-3f5563877a493a3a2060659ebe4b7aae62a17d84.tar.xz
doc: update mailing list address
Move from sourceforge to linux foundation. Also get rid of some other stale mentions of sourceforge. Github-Pull: #6319 Rebased-From: 88d8525ca2ff2afc171cd0f625a098371f3a6af5
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index fb9c0b6d77..d59767d4cc 100644
--- a/README.md
+++ b/README.md
@@ -34,7 +34,7 @@ development team members simply pulls it.
If it is a *more complicated or potentially controversial* change, then the patch
submitter will be asked to start a discussion (if they haven't already) on the
-[mailing list](http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development).
+[mailing list](https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev)
The patch will be accepted if there is broad consensus that it is a good thing.
Developers should expect to rework and resubmit patches if the code doesn't