This is an automated email from the git hooks/post-receive script.

sebastic-guest pushed a commit to branch master
in repository website.

commit e99c368870653be24ec7a3bc964688cfd8f6f06b
Author: Bas Couwenberg <>
Date:   Sat Feb 15 02:23:42 2014 +0100

    Various spelling fixes.
 policy.xml | 38 +++++++++++++++++++-------------------
 1 file changed, 19 insertions(+), 19 deletions(-)

diff --git a/policy.xml b/policy.xml
index b224b99..8b42844 100644
--- a/policy.xml
+++ b/policy.xml
@@ -54,7 +54,7 @@
       Geographical Information System applications and users.
-      A good deal of GIS related softwares and libraries (e.g. GRASS GIS, GDAL,
+      A good deal of GIS related software and libraries (e.g. GRASS GIS, GDAL,
       and PROJ.4) are already present in Debian.
@@ -102,7 +102,7 @@
       section if you're interested in joining us.
-      If you speak a language other than English, you can contribute rightaway
+      If you speak a language other than English, you can contribute right away
       with translations of package descriptions at
       <ulink url="";></ulink>.
@@ -175,7 +175,7 @@
             <ulink url="";>Debian 
GIS Policy</ulink>
-            (this document): explains how the work is organised in our team.
+            (this document): explains how the work is organized in our team.
@@ -428,7 +428,7 @@ pkg-grass/
-          Tags for package releases targetting derivative distributions use
+          Tags for package releases targeting derivative distributions use
            a distribution specific prefix followed by the package version
            separated by a <literal>/</literal> character:
@@ -872,7 +872,7 @@ Cmnd_Alias PBUILDERS=/usr/sbin/pbuilder, 
             Use <command>git-buildpackage</command>'s
-            option for building packages targetting a different architecture,
+            option for building packages targeting a different architecture,
             such as building <literal>i386</literal> packages on
@@ -884,7 +884,7 @@ Cmnd_Alias PBUILDERS=/usr/sbin/pbuilder, 
             <literal>master</literal> branch.
-            Packages targetting <link linkend="ubuntugis-ppa">UbuntuGIS</link>
+            Packages targeting <link linkend="ubuntugis-ppa">UbuntuGIS</link>
             or derivatives such as
             <ulink url="";>OSGeo-Live</ulink> can be
             built from their distribution specific branches.
@@ -915,7 +915,7 @@ Cmnd_Alias PBUILDERS=/usr/sbin/pbuilder, 
                   but the latter are reasonable when codenames are not used.
-                  If the packaging workflow benefits more from tracking 
+                  If the packaging work flow benefits more from tracking 
                   release aliases such as <literal>stable</literal>,
                   <literal>testing</literal> or <literal>unstable</literal>
                   this is also possible.
@@ -1082,7 +1082,7 @@ Cmnd_Alias PBUILDERS=/usr/sbin/pbuilder, 
             For example, when a <literal>pristine-tar</literal> branch is
             available upstream and not yet tracked locally, the command
             <command>git checkout</command> <option>pristine-tar</option>
-            will implicitely run the command
+            will implicitly run the command
             <command>git branch</command> <option>-t pristine-tar 
@@ -1295,7 +1295,7 @@ lintian ../build-area/*changes
         <ulink url="";>OSGeo-Live</ulink>)
         are profiting from our work inside Debian and we try to establish
         strong connections to these derivatives.
-        With UbuntuGIS the connection is as strong that a common workflow
+        With UbuntuGIS the connection is as strong that a common work flow
         was created where UbuntuGIS developers are injecting their packaging
         straight into the Debian GIS version control system.
         To make sure that there will be no conflicts with the Debian revisions
@@ -1317,7 +1317,7 @@ lintian ../build-area/*changes
         sometimes introduces backward incompatibilities, so the current 
         is to make packages depend on versions equal or higher to the one 
         against which they were built. When using <code>r-base-dev</code>,
-        this can be acheived by adding the substitution variable
+        this can be achieved by adding the substitution variable
         <code>${R:Depends}</code> in the <literal>Depends</literal> field of
         the binary package.
@@ -1328,7 +1328,7 @@ lintian ../build-area/*changes
       The Debian GIS
       <ulink url="";>Debian Pure 
-      is organised by
+      is organized by
       <ulink url="";>tasks</ulink>,
       that group packages around broad themes such as
       <ulink url="";>web services</ulink>
@@ -1472,7 +1472,7 @@ Vcs-Svn: 
           and <literal>libconfig-model-dpkg-perl</literal>
           and then you can simply call
           <command>cme fix</command> <option>dpkg-control</option>
-          to get a properly formated, sanity checked
+          to get a properly formatted, sanity checked
           <filename>debian/control</filename> file.
@@ -1604,7 +1604,7 @@ pristine-tar = True
     <sect2 id="debian-source-format">
-        This file sould contain <quote><literal>3.0 (quilt)</literal></quote> 
+        This file should contain <quote><literal>3.0 (quilt)</literal></quote> 
         order to use this source format.  Other formats should be avoided 
         they bring a specific advantage.
@@ -1625,7 +1625,7 @@ pristine-tar = True
     <sect2 id="debhelper">
-        Debhelper uses compatibility levels to control the behaviour of its
+        Debhelper uses compatibility levels to control the behavior of its
         commands. We currently recommend to use the level <literal>9</literal>
         which is available in current <literal>stable</literal> (Wheezy) and
         backported to <literal>oldstable</literal>. However, there is no
@@ -1635,7 +1635,7 @@ pristine-tar = True
         It is strongly recommended to use the short <literal>dh</literal> 
         notation in <filename>debian/rules</filename> files which makes code
-        factorisation very simple and easy to understand the packaging for
+        factorization very simple and easy to understand the packaging for
         other members of the team. Even complex packaging becomes quite
         transparent this way.
@@ -1644,9 +1644,9 @@ pristine-tar = True
         Before the short <literal>dh</literal> notation of debhelper existed
-        CDBS was the only way to factorise code in
+        CDBS was the only way to factorize code in
         <filename>debian/rules</filename> files.
-        We would like to standardise on <literal>dh</literal> when both
+        We would like to standardize on <literal>dh</literal> when both
         provide similar comfort. Please give it priority for new packages.
         It is also possible to switch to <literal>dh</literal> for existing
         packages, but this is entirely at the packagers discretion.
@@ -1687,7 +1687,7 @@ pristine-tar = True
       <sect3 id="vcs-svn">
         <title>Source package stored in a Subversion repository</title>
-          We often use the <literal>mergeWithUpstream</literal> workflow.
+          We often use the <literal>mergeWithUpstream</literal> work flow.
           In that case, please keep all the modifications in the
           <filename class="directory">debian</filename> directory,
           and use the <option>-o</option> option of
@@ -1745,7 +1745,7 @@ pristine-tar = True
         implies editing the source files. When you directly edit upstream's
         source files, your changes will be put into a .diff.gz file if you use
         the <literal>1.0</literal> source format and in a monolithic patch if
-        you use the <literal>3.0 (quilt)</literal> format. To better organise
+        you use the <literal>3.0 (quilt)</literal> format. To better organize
         the patches and group the by function, please use a patch handling
         system which keeps patches under the
         <filename class="directory">debian/patches</filename> directory.

Alioth's /usr/local/bin/git-commit-notice on 

Pkg-grass-devel mailing list

Reply via email to