diff --git a/README.GIT b/README.hacking similarity index 100% rename from README.GIT rename to README.hacking diff --git a/doc/faq.html b/doc/faq.html index 0f710d9f..1ccb7e0b 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -27,7 +27,7 @@ 2.1. FTP and WWW sites that carry nano.
2.2. RedHat and derivatives (.rpm) packages.
2.3. Debian (.deb) packages.
- 2.4. By GIT (for the brave). + 2.4. By git (for the brave).

3. Installation and Configuration

@@ -72,7 +72,7 @@ 7.2. How do I submit a bug report or patch?
7.3. I want to send the development team a big load of cash (or just a thank you).
7.4. How do I join the development team?
- 7.5. Can I have write access to the GIT tree? + 7.5. Can I have write access to the git tree?

@@ -121,8 +121,8 @@

You can also have a look at the Package Pool to see all the available binary and source packages.

-

2.4. By GIT (for the brave).

-

For the 'bleeding edge' current version of nano, you can use GIT to download the current source code. Note: 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 the nano GIT document for info on anonymous GIT access to the nano source.

+

2.4. By git (for the brave).

+

For the "bleeding edge" current version of nano, you can use git to download the current source code. Note: 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 the hacking document for info on getting and building nano from git.

3. Installation and Configuration