Update all references to github.

Signed-off-by: Willy Sudiarto Raharjo <willysr@gmail.com>

src/usr/doc/HACKING

@@ -3,31 +3,21 @@ SBOPKG HACKING
 INTRODUCTION
 
     We welcome contributions to sbopkg. If you have a bug report or a
-    feature request, please go to the project's Google Code site and use
+    feature request, please use the Issue Tracker so your bug report/feature
-    the Issue Tracker so your bug report/feature request does not get
+    request does not get lost.
-    lost.
 
-        http://code.google.com/p/sbopkg/issues/list
+        https://github.com/sbopkg/sbopkg/issues
 
-    If you cannot post to the Issue Tracker, please consider joining the
+    If you cannot post to the Issue Tracker, there is an #sbopkg channel on
-    sbopkg mailing list and post your bug report or feature request
-    there.
-
-        http://sbopkg.org/mailman/listinfo/sbopkg-users
-
-    If you cannot join the mailing list, there is an #sbopkg channel on
     the freenode IRC network.
 
     As far as hacking on the code, the best thing to do is to checkout
-    the latest version from subversion using something like the
+    the latest version from git using something like the
     following command:
 
-        svn checkout http://sbopkg.googlecode.com/svn/trunk \
+        git checkout https://github.com/sbopkg/sbopkg.git
-            sbopkg-contrib
 
-    (See http://www.sbopkg.org/devel.php for more information.) Then
+    Then contribute patches with something like 'diff -Naurp'.
-    contribute patches with something like 'diff -Naurp' or 'svn diff -x
-    -p'.
 
     Please try to make each patch do one thing and do it well. Also,
     please do not combine whitespace or other non-functional changes

src/usr/doc/README

@@ -57,48 +57,36 @@ GETTING HELP
     TODO              Things that may be added or modified in the future
     contrib/          Additional user-contributed files
 
-    If you have read the manuals and the relevant documents and still
-    need help, you may want to join the sbopkg mailing list. Subscribe
-    by sending a mail whose body is "subscribe your-email@address-here"
-    to:
-
-        sbopkg-users-request@sbopkg.org
-
-    or use the web interface:
-
-        http://sbopkg.org/mailman/listinfo/sbopkg-users
-
     There is also an IRC channel for sbopkg on Freenode at #sbopkg.
 
     Further information on these and other resources is on the project
     website:
 
-        http://sbopkg.org
+        https://github.com/sbopkg/sbopkg
 
     Specifically, the documentation page is:
 
-        http://sbopkg.org/docs.php
+        https://github.com/sbopkg/sbopkg/wiki
 
 CONTRIBUTING
 
     We welcome bug reports, suggestions/feature requests, and patches.
     Please post any of these to the issue tracker:
 
-        http://code.google.com/p/sbopkg/issues/list
+        https://github.com/sbopkg/sbopkg/issues
 
     Before reporting a bug, please check the KNOWN_ISSUES file. Before
     contributing a suggestion please check the TODO file. Before
     submitting a patch, please read the HACKING file.
 
-    Sbopkg's source is available in an svn repository hosted on
+    Sbopkg's source is available in an git repository hosted on
-    googlecode. To view a copy of the repo, see:
+    github. To view a copy of the repo, see:
 
-        http://code.google.com/p/sbopkg/source/browse/
+        https://github.com/sbopkg/sbopkg
 
     To obtain a local copy, use something like the following command:
 
-        svn checkout http://sbopkg.googlecode.com/svn/trunk/ \
+        git checkout https://github.com/sbopkg/sbopkg.git
-            sbopkg-contrib
 
     There have been many contributors so far (see the THANKS file).
     Thanks to everyone who has helped make this script better.

src/usr/doc/README-queuefiles

@@ -9,11 +9,6 @@ and have not necessarily been tested on the latest release of Slackware
 or on Slackware -current. If you wish to use these at your own risk,
 remove the '.sample' extension and either put them in $QUEUEDIR or set
 QUEUEDIR to where they are (see sbopkg.conf(5) for details).
-Additionally, the hope is that user-contributed queues can be shared.
-Please consider sending a copy of your queuefile(s) to the sbopkg
-mailing list:
-
-    http://sbopkg.org/mailman/listinfo/sbopkg-users
 
 SELECTING ON OR OFF IN DIALOG
 

tools/slack-desc

@@ -12,7 +12,7 @@ sbopkg: Sbopkg is a command-line and dialog-based tool to interact with the
 sbopkg: SlackBuilds.org repository, a collection of third-party SlackBuild
 sbopkg: scripts to build Slackware packages.
 sbopkg:
-sbopkg: Homepage:  http://www.sbopkg.org
+sbopkg: Homepage:  https://github.com/sbopkg/sbopkg
 sbopkg:
 sbopkg:
 sbopkg:

tools/sspm

@@ -8,7 +8,7 @@ script=${0##*/}
 # USER-MODIFIABLE VARIABLES
 # this needs to be where the checked out svn directory is.
 repo="/tmp/sbopkg-read-only"
-remote_repo="http://sbopkg.googlecode.com/svn/trunk/"
+remote_repo="https://github.com/sbopkg/sbopkg.git"
 export OUTPUT="${OUTPUT:-/tmp}"
 
 usage() {
@@ -56,7 +56,7 @@ fi
 
 if [[ $sync == yes ]]; then
     if [[ -w $repo ]] || [[ ! -e $repo && -w ${repo%/*} ]]; then
-        svn checkout $remote_repo $repo || printe "checkout failed"
+        git checkout $remote_repo $repo || printe "checkout failed"
     else
         printe "$repo is not writable.\nChange your privileges or the \
             value of the \"repo\" variable.\n"
@@ -68,11 +68,11 @@ fi
 # old package. But, as the doctor said to the guy who complained that it hurt
 # when he did that, don't DO that.
 if [[ $build == yes || $inst == yes ]]; then
-    svn_script="$repo/src/usr/sbin/sbopkg"
+    git_script="$repo/src/usr/sbin/sbopkg"
-    if [ -r $svn_script ]; then
+    if [ -r $git_script ]; then
-        export VERSION=svn$(svnversion $repo)
+        export VERSION=git$(gitversion $repo)
     else
-        printe "unable to find $svn_script.\nPlease check your repository."
+        printe "unable to find $git_script.\nPlease check your repository."
     fi
 
     if [[ $OUTPUT =~ "$repo/(sbopkg-$VERSION|root-tools)" ]]; then