44 <title>The Source Code Repository</title>
55
66 <para>
7- The <productname>PostgreSQL</productname> source code is stored and managed using the
8- <productname>Git</productname> version control system. An public mirror of this
9- is available and updated within a minute of the master repository.
7+ The <productname>PostgreSQL</productname> source code is stored and managed
8+ using the <productname>Git</productname> version control system. A public
9+ mirror of the master repository is available; it is updated within a minute
10+ of any change to the master repository.
1011 </para>
1112
1213 <para>
1314 Our wiki, <ulink
1415 url="http://wiki.postgresql.org/wiki/Working_with_Git"></ulink>,
15- has additional details on working with Git.
16+ has some discussion on working with Git.
1617 </para>
1718
1819 <para>
1920 Note that building <productname>PostgreSQL</productname> from the source
20- repository requires reasonably up-to-date versions of <application>bison</>
21- and <application>flex </>. These tools are not needed to build from a
22- distribution tarball since their output is included in the file.
23- You will need Perl as well, but otherwise the tool requirements are the
24- same .
21+ repository requires reasonably up-to-date versions of <application>bison</>,
22+ <application>flex</>, and <application>Perl </>. These tools are not needed
23+ to build from a distribution tarball since the files they are used to build
24+ are included in the tarball. Other tool requirements are the same as shown
25+ in <xref linkend="installation"> .
2526 </para>
2627
2728 <sect1 id="git">
2829 <title>Getting The Source Via <productname>Git</></title>
2930
3031 <para>
3132 With <productname>Git</> you will make a copy of the entire code repository
32- to your local machine, so you will have access to all history and branches
33+ on your local machine, so you will have access to all history and branches
3334 offline. This is the fastest and most flexible way to develop or test
3435 patches.
3536 </para>
3940
4041 <step>
4142 <para>
42- You will need an installed version of <productname>Git</>, which you can get
43- from <ulink url="http://git-scm.com"></ulink>. Many systems also have a recent
44- version of <application>Git</> installed by default, or available in their
45- package repository system.
43+ You will need an installed version of <productname>Git</>, which you can
44+ get from <ulink url="http://git-scm.com"></ulink>. Many systems already
45+ have a recent version of <application>Git</> installed by default, or
46+ available in their package distribution system.
4647 </para>
4748 </step>
4849
4950 <step>
5051 <para>
51- To being using the Git repository, make a clone of the official mirror:
52+ To begin using the Git repository, make a clone of the official mirror:
5253
5354<programlisting>
5455git clone git://git.postgresql.org/git/postgresql.git
5556</programlisting>
5657
5758 This will copy the full repository to your local machine, so it may take
5859 a while to complete, especially if you have a slow Internet connection.
60+ The files will be placed in a new subdirectory <filename>postgresql</> of
61+ your current directory.
5962 </para>
6063
6164 <para>
62- The Git mirror can also be reached via the HTTP protocol in case for example
63- a firewall is blocking access to the Git protocol. Just replace the URL
64- like :
65+ The Git mirror can also be reached via the HTTP protocol, if for example
66+ a firewall is blocking access to the Git protocol. Just change the URL
67+ prefix to <literal>http</>, as in :
6568
6669<programlisting>
6770git clone http://git.postgresql.org/git/postgresql.git
@@ -83,10 +86,11 @@ git fetch
8386 </para>
8487 </step>
8588 </procedure>
89+
8690 <para>
8791 <productname>Git</> can do a lot more things than just fetch the source. For
88- more information, consult the man pages for the product , or the website at
89- <ulink url="http://git-scm.com"></>.
92+ more information, consult the <productname>Git</> man pages, or see the
93+ website at <ulink url="http://git-scm.com"></>.
9094 </para>
9195 </sect1>
9296
0 commit comments