more svn->git updates

Makefile.am

@@ -2,6 +2,6 @@ AUTOMAKE_OPTIONS = gnu no-dependencies
 
 SUBDIRS = doc m4 po src
 
-EXTRA_DIST = ChangeLog.pre-2.1 README.SVN UPGRADE nano.spec
+EXTRA_DIST = ChangeLog.pre-2.1 README.GIT UPGRADE nano.spec
 
 ACLOCAL_AMFLAGS = -I m4

autogen.sh

@@ -1,4 +1,4 @@
 #!/bin/sh
-# Generate configure & friends for SVN users.
+# Generate configure & friends for GIT users.
 
 autoreconf -f -i -s

doc/faq.html

@@ -19,7 +19,7 @@
 <blockquote><p><a href="#2.1">2.1. FTP and WWW sites that carry nano.</a><br>
   <a href="#2.2">2.2. RedHat and derivatives (.rpm) packages.</a><br>
   <a href="#2.3">2.3. Debian (.deb) packages.</a><br>
-  <a href="#2.4">2.4. By subversion (for the brave).</a></p></blockquote>
+  <a href="#2.4">2.4. By GIT (for the brave).</a></p></blockquote>
 <h2><a href="#3">3. Installation and Configuration</a></h2>
 <blockquote><p><a href="#3.1">3.1. How do I install the RPM or DEB package?</a><br>
   <a href="#3.2">3.2. Compiling from source: WHAT THE HECK DO I DO NOW?</a><br>
@@ -61,7 +61,7 @@
   <a href="#7.2">7.2. I want to send the development team a big load of cash (or just a thank you).</a><br>
   <a href="#7.3">7.3. How do I submit a bug report or patch?</a><br>
   <a href="#7.4">7.4. How do I join the development team?</a><br>
-  <a href="#7.5">7.5. Can I have write access to the subversion tree?</a></p></blockquote>
+  <a href="#7.5">7.5. Can I have write access to the GIT tree?</a></p></blockquote>
 <h2><a href="#8">8. ChangeLog</a></h2>
 <hr width="100%">
 <h1><a name="1"></a>1. General</h1>
@@ -111,8 +111,8 @@
   </ul>
   <p>You can also have a look at the <a href="ftp://ftp.debian.org/debian/pool/main/n/nano/">Package Pool</a> to see all the available binary and source packages.</p>
 </blockquote>
-<h2><a name="2.4"></a>2.4. By subversion (for the brave).</h2>
+<h2><a name="2.4"></a>2.4. By GIT (for the brave).</h2>
-<blockquote><p>For the 'bleeding edge' current version of nano, you can use subversion to download the current source code. <b>Note:</b> believe it or not, by downloading code that has not yet stabilized into an official release, there could quite possibly be bugs, in fact the code may not even compile! Anyway, see <a href="http://svn.savannah.gnu.org/viewvc/trunk/nano/README.SVN?root=nano&view=markup">the nano SVN document</a> for info on anonymous SVN access to the nano source.</p></blockquote>
+<blockquote><p>For the 'bleeding edge' current version of nano, you can use GIT to download the current source code. <b>Note:</b> believe it or not, by downloading code that has not yet stabilized into an official release, there could quite possibly be bugs, in fact the code may not even compile! Anyway, see <a href="http://git.savannah.gnu.org/cgit/nano.git/tree/README.GIT">the nano GIT document</a> for info on anonymous GIT access to the nano source.</p></blockquote>
 <hr width="100%">
 <h1><a name="3"></a>3. Installation and Configuration</h1>
 <h2><a name="3.1"></a>3.1. How do I install the RPM or DEB package?</h2>
@@ -254,11 +254,12 @@ Of course, due to the license change you can now use the <A HREF="http://www.was
 <p>The best place to submit bugs is to the <a href="https://savannah.gnu.org/bugs/?group=nano">Savannah bug tracker</a> as you can check whether the bug you are submitting has already been submitted.
 <p>Please submit patches for nano via the <a href="https://savannah.gnu.org/patch/?group=nano">Savannah project's patch manager</a> for the nano project.</p></blockquote>
 <h2><a name="7.4"></a>7.4. How do I join the development team?</h2>
-<blockquote><p>The easiest way is to consistently send in good patches that add some needed functionality, fix a bug or two, and/or make the program more optimized/efficient. Then ask nicely and you will probably be added to the Savannah development list and be given SVN write access after a while. There is a lot of responsibility that goes along with being a team member, so don't think it's just something to add to your resume.</p></blockquote>
+<blockquote><p>The easiest way is to consistently send in good patches that add some needed functionality, fix a bug or two, and/or make the program more optimized/efficient. Then ask nicely and you will probably be added to the Savannah development list and be given write access after a while. There is a lot of responsibility that goes along with being a team member, so don't think it's just something to add to your resume.</p></blockquote>
-<h2><a name="7.5"></a>7.5. Can I have write access to the subversion tree?</h2>
+<h2><a name="7.5"></a>7.5. Can I have write access to the git tree?</h2>
 <blockquote><p>Re-read Section <a href="#7.4">7.4</a> and you should know the answer.</p></blockquote>
 <h2><a name="8"></a>8. ChangeLog</h2>
 <blockquote><p>
+2016/04/17 - Update docs to refer to GIT instead of subversion. (Mike)<br>
 2015/07/18 - More small fixes and updates. (Benno)<br>
 2014/04/24 - A bunch of small fixes and updates. (Benno)<br>
 2009/11/30 - Update various bits for nano 2.2.x. (DLR)<br>

po/update_linguas.sh

@@ -1,21 +1,16 @@
 #!/bin/sh
+cd "$(dirname "$0")" || exit
 echo "Updating translations via TP" && \
 rsync -Lrtvz  translationproject.org::tp/latest/nano/ .
-#
+git add -v *.po
-NEWSTUFF=`svn status | grep "^\? .*.po$" | awk '{ print $NF }'`
-if [ "x$NEWSTUFF" != "x" ]; then
-    echo "Adding new languaes to SVN"
-    svn add $NEWSTUFF
-fi
-#
 echo "Updating LINGUAS for all translations"
 FILE=LINGUAS
-echo "# List of available languages." >$FILE
+echo "# List of available languages." >"${FILE}"
-/bin/ls *.po | tr '\n' ' ' | sed 's/\.po//g' >>$FILE
+echo $(printf '%s\n' *.po | LC_ALL=C sort | sed 's/\.po//g') >>"${FILE}"
-echo >> $FILE
+git add -v "${FILE}"
-#
+NEWSTUFF=$(git status --porcelain *.po)
-if [ "x$NEWSTUFF" != "x" ]; then
+if [ -n "${NEWSTUFF}" ]; then
-    echo -n "New langs found, re-running configure and make at top level (silently)..."
+    printf "New langs found, re-running configure and make at top level (silently)..."
     (cd .. && ./configure  && make) >/dev/null
     echo "done"
 fi