summaryrefslogtreecommitdiff
path: root/docs/CONTRIBUTE.md
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2020-11-04 14:02:01 +0100
committerDaniel Stenberg <daniel@haxx.se>2020-11-04 23:59:47 +0100
commit4d2f8006777d6354d9b62eae38ebd0a0256d0f94 (patch)
tree31f6a88fdf1b3d96f52f7e5c008a7e966c7d218d /docs/CONTRIBUTE.md
parent0673cb4d2d97360c68a6ac237eab14fc154bc384 (diff)
downloadcurl-4d2f8006777d6354d9b62eae38ebd0a0256d0f94.tar.gz
curl.se: new home
Closes #6172
Diffstat (limited to 'docs/CONTRIBUTE.md')
-rw-r--r--docs/CONTRIBUTE.md18
1 files changed, 9 insertions, 9 deletions
diff --git a/docs/CONTRIBUTE.md b/docs/CONTRIBUTE.md
index 69ddfbee0..6b86b25c4 100644
--- a/docs/CONTRIBUTE.md
+++ b/docs/CONTRIBUTE.md
@@ -8,14 +8,14 @@ flaws or bugs.
### Join the Community
-Skip over to [https://curl.haxx.se/mail/](https://curl.haxx.se/mail/) and join
+Skip over to [https://curl.se/mail/](https://curl.se/mail/) and join
the appropriate mailing list(s). Read up on details before you post
questions. Read this file before you start sending patches! We prefer
questions sent to and discussions being held on the mailing list(s), not sent
to individuals.
Before posting to one of the curl mailing lists, please read up on the
-[mailing list etiquette](https://curl.haxx.se/mail/etiquette.html).
+[mailing list etiquette](https://curl.se/mail/etiquette.html).
We also hang out on IRC in #curl on irc.freenode.net
@@ -49,12 +49,12 @@ always provide us with your full real name when contributing!
### What To Read
Source code, the man pages, the [INTERNALS
-document](https://curl.haxx.se/dev/internals.html),
-[TODO](https://curl.haxx.se/docs/todo.html),
-[KNOWN_BUGS](https://curl.haxx.se/docs/knownbugs.html) and the [most recent
-changes](https://curl.haxx.se/dev/sourceactivity.html) in git. Just lurking on
+document](https://curl.se/dev/internals.html),
+[TODO](https://curl.se/docs/todo.html),
+[KNOWN_BUGS](https://curl.se/docs/knownbugs.html) and the [most recent
+changes](https://curl.se/dev/sourceactivity.html) in git. Just lurking on
the [curl-library mailing
-list](https://curl.haxx.se/mail/list.cgi?list=curl-library) will give you a
+list](https://curl.se/mail/list.cgi?list=curl-library) will give you a
lot of insights on what's going on right now. Asking there is a good idea too.
## Write a good patch
@@ -62,7 +62,7 @@ lot of insights on what's going on right now. Asking there is a good idea too.
### Follow code style
When writing C code, follow the
-[CODE_STYLE](https://curl.haxx.se/dev/code-style.html) already established in
+[CODE_STYLE](https://curl.se/dev/code-style.html) already established in
the project. Consistent style makes code easier to read and mistakes less
likely to happen. Run `make checksrc` before you submit anything, to make sure
you follow the basic style. That script doesn't verify everything, but if it
@@ -131,7 +131,7 @@ verified your changes.
Ideally you file a [pull request on
github](https://github.com/curl/curl/pulls), but you can also send your plain
patch to [the curl-library mailing
-list](https://curl.haxx.se/mail/list.cgi?list=curl-library).
+list](https://curl.se/mail/list.cgi?list=curl-library).
Either way, your change will be reviewed and discussed there and you will be
expected to correct flaws pointed out and update accordingly, or the change