---
contrib.html | 6 +++---
cvs.html | 20 ++++++++++----------
cygwin-ug-net/setup-net.html | 4 ++--
faq/faq.html | 2 +-
git.html | 28 ++++++++++++++--------------
lists.html | 4 ++--
navbar.html | 2 +-
7 files changed, 33 insertions(+), 33 deletions(-)
diff --git a/contrib.html b/contrib.html
index 375ba3a..5d6514d 100755
--- a/contrib.html
+++ b/contrib.html
@@ -48,7 +48,7 @@ contribution rules. See their project pages for more
information.</p>
directory with additional code coming from newlib/libc and newlib/libm.
Any changes you make should be to the <a href="git.html">current
development sources</a>. This makes it much easier to integrate your
-changes once they're completed and tested. Note that the current GIT
+changes once they're completed and tested. Note that the current Git
tree (and the development snapshots) should compile, but they should
always be assumed to be unstable since they contain untested,
experimental code.
@@ -56,8 +56,8 @@ experimental code.
<P>Build instructions are included in the <a href="faq.html">FAQ</a> under
"How do I build Cygwin on my own?".
-<p>Basically, just clone the newlib-cygwin GIT repository as mentioned on the
-Cygwin <a href="git.html">GIT page</a>.
+<p>Basically, just clone the newlib-cygwin Git repository as mentioned on the
+Cygwin <a href="git.html">Git page</a>.
<div id="background">
<b class="rtop"><b class="r1"></b><b class="r2"></b><b class="r3"></b><b
class="r4"></b></b>
diff --git a/cvs.html b/cvs.html
index 915880b..c090c72 100755
--- a/cvs.html
+++ b/cvs.html
@@ -3,51 +3,51 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<link rel="stylesheet" type="text/css" href="style.css" />
- <title>Cygwin in GIT</title>
+ <title>Cygwin in Git</title>
</head>
<body>
<!--#include virtual="navbar.html" -->
<!--#include virtual="top.html" -->
-<h1>Cygwin in GIT</h1>
+<h1>Cygwin in Git</h1>
<p>The sources to the core Cygwin libraries and utilities (Cygwin and
-Newlib) are available via anonymous GIT access. If you don't know
-what GIT is, visit the <a href="http://git-scm.com/";>GIT home page</a>.
-Coincidentally enough, GIT comes with the Cygwin net release.</p>
+Newlib) are available via anonymous Git access. If you don't know
+what Git is, visit the <a href="http://git-scm.com/";>Git home page</a>.
+Coincidentally enough, Git comes with the Cygwin net release.</p>
<p>To access the repository from your system, use one of the following
commands:</p>
<dl>
-<dt><b>Read-only web-based GIT access</b></dt>
+<dt><b>Read-only web-based Git access</b></dt>
<dd>
<p>You can use <a href="/git/gitweb.cgi?p=newlib-cygwin.git" target=_top>the
gitweb interface</a>.
</dd>
-<dt><b>Anonymous GIT read-only access</b></dt>
+<dt><b>Anonymous Git read-only access</b></dt>
<dd>
<pre>
git clone git://sourceware.org/git/newlib-cygwin.git
</pre>
</dd>
-<dt><b>GIT for developers with read/write access</b></dt>
+<dt><b>Git for developers with read/write access</b></dt>
<dd>
<pre>
git clone sourceware.org:/git/newlib-cygwin.git
</pre>
</dd>
-<dt><b>GIT-less Developer snapshots</b></dt>
+<dt><b>Git-less Developer snapshots</b></dt>
<dd>
<p>Developer snapshots are available via
<a href="snapshots.html" target=_top>the Cygwin developer snapshot page</a>.
New snapshots are packaged and released from time to time as required for
testing of new features. The matching sources are provided alongside the
binary tar archives. This allows following development even if you're not
- comfortable with GIT.
+ comfortable with Git.
</p>
</dd>
diff --git a/cygwin-ug-net/setup-net.html b/cygwin-ug-net/setup-net.html
index 8c3034a..05a579c 100644
--- a/cygwin-ug-net/setup-net.html
+++ b/cygwin-ug-net/setup-net.html
@@ -22,8 +22,8 @@ for new users to understand while remaining flexible for the
experienced. The volunteer development team is constantly working
on <span class="command"><strong>setup.exe</strong></span>; before requesting
a new feature,
check the wishlist in the
-<a class="ulink"
href="https://sourceware.org/git/gitweb.cgi?p=cygwin-setup.git;a=blob_plain;f=README;hb=HEAD";
target="_top">GIT <code class="literal">README</code>
-</a>. It may already be present in the GIT version!
+<a class="ulink"
href="https://sourceware.org/git/gitweb.cgi?p=cygwin-setup.git;a=blob_plain;f=README;hb=HEAD";
target="_top">Git <code class="literal">README</code>
+</a>. It may already be present in the Git version!
</p><p>
On Windows Vista and later, <span
class="command"><strong>setup.exe</strong></span> will check by
default if it runs with administrative privileges and, if not, will try
diff --git a/faq/faq.html b/faq/faq.html
index 6318b9d..90738ab 100644
--- a/faq/faq.html
+++ b/faq/faq.html
@@ -1971,7 +1971,7 @@ which requires the <code class="literal">dblatex</code>,
<code class="literal">xmlto</code> packages. For more information on building
the
documentation, see the README included in the <code
class="literal">cygwin-doc</code> package.
</p><p>Next, get the Cygwin source. Ideally, you should check out what you
-need from GIT (<a class="ulink" href="https://cygwin.com/git.html";
target="_top">https://cygwin.com/git.html</a>). This is the
+need from Git (<a class="ulink" href="https://cygwin.com/git.html";
target="_top">https://cygwin.com/git.html</a>). This is the
<span class="emphasis"><em>preferred method</em></span> for acquiring the
sources. Otherwise,
if you are trying to duplicate a cygwin release then you should download the
corresponding source package
diff --git a/git.html b/git.html
index 7fee05d..6b1af0c 100755
--- a/git.html
+++ b/git.html
@@ -3,63 +3,63 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<link rel="stylesheet" type="text/css" href="style.css" />
- <title>Cygwin in GIT</title>
+ <title>Cygwin in Git</title>
</head>
<body>
<!--#include virtual="navbar.html" -->
<!--#include virtual="top.html" -->
-<h1>Cygwin in GIT</h1>
+<h1>Cygwin in Git</h1>
<p>The sources to the core Cygwin libraries and utilities (Cygwin and
-Newlib) are available via anonymous GIT access. If you don't know
-what GIT is, visit the <a href="http://git-scm.com/";>GIT home page</a>.
-Coincidentally enough, GIT comes with the Cygwin net release.</p>
+Newlib) are available via anonymous Git access. If you don't know
+what Git is, visit the <a href="http://git-scm.com/";>Git home page</a>.
+Coincidentally enough, Git comes with the Cygwin net release.</p>
<p>To access the repository from your system, use one of the following
commands:</p>
<dl>
-<dt><b>Read-only web-based GIT access</b></dt>
+<dt><b>Read-only web-based Git access</b></dt>
<dd>
<p>You can use <a href="/git/gitweb.cgi?p=newlib-cygwin.git" target=_top>the
gitweb interface</a>.
</dd>
-<dt><b>Anonymous GIT read-only access</b></dt>
+<dt><b>Anonymous Git read-only access</b></dt>
<dd>
<pre>
git clone git://sourceware.org/git/newlib-cygwin.git
</pre>
</dd>
-<dt><b>GIT for developers with read/write access</b></dt>
+<dt><b>Git for developers with read/write access</b></dt>
<dd>
<pre>
git clone sourceware.org:/git/newlib-cygwin.git
</pre>
</dd>
-<dt><b>GIT-less Developer snapshots</b></dt>
+<dt><b>Git-less Developer snapshots</b></dt>
<dd>
<p>Developer snapshots are available via
<a href="snapshots" target=_top>the Cygwin developer snapshot page</a>.
New snapshots are packaged and released from time to time as required for
testing of new features. The matching sources are provided alongside the
binary tar archives. This allows following development even if you're not
- comfortable with GIT.
+ comfortable with Git.
</p>
</dd>
-<dt><b>GIT access to the website</b></dt>
+<dt><b>Git access to the website</b></dt>
<dd>
- <p>The cygwin.com website is under GIT control, too. You can view the
- website GIT repo via
+ <p>The cygwin.com website is under Git control, too. You can view the
+ website Git repo via
<a href="git/gitweb.cgi?p=cygwin-htdocs.git">its gitweb interface</a>.
<br>
Note that this is only the framework.
<a href="git/gitweb.cgi?p=newlib-cygwin.git;a=tree;f=winsup/doc">User's
Guide, API and FAQ</a>
- are maintained as part of the aforementioned Cygwin source GIT repository.
+ are maintained as part of the aforementioned Cygwin source Git repository.
</p>
</dd>
diff --git a/lists.html b/lists.html
index 978787d..8b8eb00 100755
--- a/lists.html
+++ b/lists.html
@@ -137,14 +137,14 @@ viruses. This means that your information will be
viewable by posterity, so
</li>
<p><li><a name="cygwin-cvs"><a
href="/ml/cygwin-cvs/"><b>cygwin-cvs</b></a></a>:
- a read-only list which receives log messages for every GIT commit in the
+ a read-only list which receives log messages for every Git commit in the
'winsup' directory. If you don't know what this means then you probably
shouldn't subscribe. Messages consist of a log message and pointers to
diffs of the changes.
</li>
<p><li><a name="cygwin-apps-cvs"><a
href="/ml/cygwin-apps-cvs/"><b>cygwin-apps-cvs</b></a></a>:
- a list which receives log messages for every GIT and CVS commit in the
+ a list which receives log messages for every Git and CVS commit in the
'cygwin-apps' repository. If you don't know what this means then you
probably shouldn't subscribe. Messages consist of a log message and
pointers to diffs of the changes.
diff --git a/navbar.html b/navbar.html
index f869b92..3bec270 100644
--- a/navbar.html
+++ b/navbar.html
@@ -30,7 +30,7 @@
<ul>
<li><a href="http://cygwin.com/contrib.html";>Contributing</a></li>
<li><a href="http://cygwin.com/snapshots/";> Snapshots</a></li>
-<li><a href="http://cygwin.com/git.html";> Source in
GIT</a></li>
+<li><a href="http://cygwin.com/git.html";> Source in
Git</a></li>
<li><a href="http://cygwin.com/setup.html";> Cygwin
Packages</a></li>
</ul>
<ul>
--
2.8.0
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
