Update github links.

diff --git a/bin/badge-update b/bin/badge-update
index 7be23038a136cad7490c5e1cad504eb54300d6f8..2b5b72ad8471bdadb2f002fb0bf946d0ec4ffc28 100755 (executable)
--- a/bin/badge-update
+++ b/bin/badge-update
@@ -1,4 +1,4 @@
 #!/bin/sh
 rm -f badge.svg
-wget https://github.com/WayneD/rsync/workflows/build/badge.svg
+wget https://github.com/RsyncProject/rsync/workflows/build/badge.svg
 rsync -aiic --inplace --remove-source-files badge.svg $SAMBA_HOST:/home/httpd/html/rsync/

diff --git a/bug-tracking.html b/bug-tracking.html
index 3b14833c4c2da10ab71ff3b5e00c115f18ee4e9c..75e6c7689be2a2f62ebb65be656d46b33c604e4e 100644 (file)
--- a/bug-tracking.html
+++ b/bug-tracking.html
@@ -17,11 +17,11 @@ reporting a bug.  Thanks!
 reporting a bug.
 
 <li> If you're using the latest released version, consult the
-<a href="https://github.com/WayneD/rsync/blob/master/NEWS.md">NEWS file from the git repository</a> to see if what
+<a href="https://github.com/RsyncProject/rsync/blob/master/NEWS.md">NEWS file from the git repository</a> to see if what
 you're seeing has already been handled in the version under development.
 
 <li> It is also helpful to search the bug reports at both the new
-<a href="https://github.com/WayneD/rsync/issues?q=is%3Aissue">GitHub issues tracker</a> and the old
+<a href="https://github.com/RsyncProject/rsync/issues?q=is%3Aissue">GitHub issues tracker</a> and the old
 <a href="https://bugzilla.samba.org/buglist.cgi?product=rsync&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED">bugzilla database</a>
 to see if the problem is already known.
 
@@ -35,7 +35,7 @@ help diagnose what is going wrong.
 you're seeing is really a bug or a mistake.
 
 <li>There are several patches for features that are under consideration that
-can be found in the <a href="https://github.com/WayneD/rsync-patches">rsync-patches repo</a>.
+can be found in the <a href="https://github.com/RsyncProject/rsync-patches">rsync-patches repo</a>.
 
 <li> If you haven't already done so, please take a couple of minutes to read Simon Tatham's
 <a href="https://www.chiark.greenend.org.uk/~sgtatham/bugs.html">advice on how to report bugs</a>.
@@ -54,7 +54,7 @@ no mandate to use pull requests for patches, as that can be a pretty high
 bar of git know-how that not everyone needs to be familiar with.
 
 <li> If you'd like to see a bug-report or feature-request get officially noted,
-<a href="https://github.com/WayneD/rsync/issues">create an issue on GitHub</a>
+<a href="https://github.com/RsyncProject/rsync/issues">create an issue on GitHub</a>
 (this does require that you have created a GitHub account).  If you want to
 stay abreast of what's going on with the issues, make use of the GitHub
 subscriptions to pick and choose what kind of notifications you want to

diff --git a/download.html b/download.html
index 7b9218159769aa80491d7391e0efac06394889d2..1d43ee5d59151a64d11a608f758abdc585f75bbd 100644 (file)
--- a/download.html
+++ b/download.html
@@ -8,7 +8,7 @@
 <h2 align="center">rsync download</h2>
 
 <div style="float: right">
-<a href="https://github.com/WayneD/rsync/actions">
+<a href="https://github.com/RsyncProject/rsync/actions">
 <img src="badge.svg">
 </a></div>
 
@@ -26,14 +26,14 @@ via <i>anonymous SSL rsync</i> using this command:
 <p><code><small>rsync-ssl rsync://download.samba.org/rsyncftp/</small></code></p>
 
 <li><p>You can also get .zip and .tar.gz versions of the various git repo's release
-tags via the <a href="https://github.com/WayneD/rsync/releases">rsync GitHub releases page</a>
+tags via the <a href="https://github.com/RsyncProject/rsync/releases">rsync GitHub releases page</a>
 and the associated patches via the
-<a href="https://github.com/WayneD/rsync-patches/releases">rsync-patches GitHub releases page</a>.
+<a href="https://github.com/RsyncProject/rsync-patches/releases">rsync-patches GitHub releases page</a>.
 Keep in mind that these git-derived files do NOT come with the extra generated files that are included
 in the official release tar files.
 
 <li><p>You can browse the very latest source files, clone the source using git, or download a .zip file of the latest
-master branch from <a href="https://github.com/WayneD/rsync">rsync's GitHub page</a>.
+master branch from <a href="https://github.com/RsyncProject/rsync">rsync's GitHub page</a>.
 
 <li><p>The <a href="https://git.samba.org/?p=rsync.git">Samba git repo</a> is also available,
 though it might lag behind the GitHub repo every now and then.
@@ -58,7 +58,7 @@ key for Wayne Davison</a> manually.
 you should first check if you can install an rsync package via your
 standard package-install tools for your OS.
 
-<p>The <a href="https://github.com/WayneD/rsync/actions">GitHub Actions
+<p>The <a href="https://github.com/RsyncProject/rsync/actions">GitHub Actions
 page</a> has build events that each generate a few binary artifact zip files
 (just click through via the build's title to see them).  The actions page is
 also linked via the various green build-status icons on the web pages here.

diff --git a/index.html b/index.html
index 4b14cd00ef3c076bf2dba2e5cda7c8a7dfc2a45d..83f2a6f88cc40516cd6771fbfc33e471dcef5355 100644 (file)
--- a/index.html
+++ b/index.html
@@ -22,7 +22,7 @@ License</A> and is currently being maintained by
 <a href="https://download.samba.org/pub/rsync/NEWS">NEWS file</a>.
 
 <div style="float: right">
-<a href="https://github.com/WayneD/rsync/actions">
+<a href="https://github.com/RsyncProject/rsync/actions">
 <img src="badge.svg">
 </a></div>