Skip to content

Commit

Permalink
Regenerated install docs.
Browse files Browse the repository at this point in the history
  • Loading branch information
timlinux committed Jun 12, 2011
2 parents 512bc17 + 30e0a52 commit 62714a8
Show file tree
Hide file tree
Showing 20 changed files with 1,366 additions and 2,849 deletions.
6 changes: 3 additions & 3 deletions CODING
Original file line number Diff line number Diff line change
Expand Up @@ -596,10 +596,10 @@ easily, and help us deal with the patches that are sent to use easily.

If the patch is a fix for a specific bug, please name the file with the bug
number in it e.g. bug777fix.patch, and attach it to the original bug report
in trac (https://trac.osgeo.org/qgis/).
in trac (http://hub.qgis.org/projects/quantum-gis).

If the bug is an enhancement or new feature, its usually a good idea to create
a ticket in trac (https://trac.osgeo.org/qgis/) first and then attach you
a ticket in trac (http://hub.qgis.org/projects/quantum-gis) first and then attach you


2.7.2. Create your patch in the top level QGIS source dir
Expand Down Expand Up @@ -868,7 +868,7 @@ test before fixing the bug will let you automate the testing for bug
resolution in an efficient manner.

To implement your regression test, you should follow the naming convention of
regression<TicketID> for your test functions. If no trac ticket exists for the
regression<TicketID> for your test functions. If no redmine ticket exists for the
regression, you should create one first. Using this approach allows the person
running a failed regression test easily go and find out more information.

Expand Down
Binary file modified CODING.pdf
Binary file not shown.
Binary file modified INSTALL.pdf
Binary file not shown.
6 changes: 3 additions & 3 deletions doc/CODING.t2t
Original file line number Diff line number Diff line change
Expand Up @@ -575,10 +575,10 @@ easily, and help us deal with the patches that are sent to use easily.

If the patch is a fix for a specific bug, please name the file with the bug
number in it e.g. **bug777fix.patch**, and attach it to the original bug report
in trac (https://trac.osgeo.org/qgis/).
in trac (http://hub.qgis.org/projects/quantum-gis).

If the bug is an enhancement or new feature, its usually a good idea to create
a ticket in trac (https://trac.osgeo.org/qgis/) first and then attach you
a ticket in trac (http://hub.qgis.org/projects/quantum-gis) first and then attach you

=== Create your patch in the top level QGIS source dir ===

Expand Down Expand Up @@ -854,7 +854,7 @@ test **before** fixing the bug will let you automate the testing for bug
resolution in an efficient manner.

To implement your regression test, you should follow the naming convention of
regression<TicketID> for your test functions. If no trac ticket exists for the
regression<TicketID> for your test functions. If no redmine ticket exists for the
regression, you should create one first. Using this approach allows the person
running a failed regression test easily go and find out more information.

Expand Down
1 change: 1 addition & 0 deletions doc/CONTRIBUTORS
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,7 @@ Richard Duivenvoorde
Richard Kostecky
Robert Szczepanek
Stefanie Tellex
Steven Mizuno
Tom Russo
Tyler Mitchell
Vita Cizek
Expand Down
2 changes: 1 addition & 1 deletion doc/index.dox
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ developers.</li> </ul>

\section index_bugs Bug Reporting
If you think you have found a bug, please report it using our <a
href="https://trac.osgeo.org/qgis/">bug tracker</a>. When reporting bugs,
href="http://hub.qgis.org/projects/quantum-gis">bug tracker</a>. When reporting bugs,
please include some contact information in case we need help with replicating
your issue.

Expand Down
Loading

0 comments on commit 62714a8

Please sign in to comment.