summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--Bugzilla/User.pm2
-rw-r--r--contrib/README.Mailif2
-rwxr-xr-xcontrib/bug_email.pl10
-rw-r--r--contrib/bugmail_help.html16
-rwxr-xr-xcontrib/gnatsparse/gnatsparse.py2
-rwxr-xr-xprocess_bug.cgi2
6 files changed, 17 insertions, 17 deletions
diff --git a/Bugzilla/User.pm b/Bugzilla/User.pm
index 0cca45682..d35077a4b 100644
--- a/Bugzilla/User.pm
+++ b/Bugzilla/User.pm
@@ -1488,7 +1488,7 @@ the page footer, and C<0> otherwise.
=item C<identity>
-Retruns a string for the identity of the user. This will be of the form
+Returns a string for the identity of the user. This will be of the form
C<name E<lt>emailE<gt>> if the user has specified a name, and C<email>
otherwise.
diff --git a/contrib/README.Mailif b/contrib/README.Mailif
index 8b6604438..0c65cef83 100644
--- a/contrib/README.Mailif
+++ b/contrib/README.Mailif
@@ -54,7 +54,7 @@ Search the script after 'default' - you find some default-Settings for bug
reports, which are used, if the sender did not send a field for it. The defaults
should be checked and changed.
-Thats hopefully all, we will come up with any configuration file or something.
+That's hopefully all, we will come up with any configuration file or something.
If your mail works, your script will insert mails from now on.
diff --git a/contrib/bug_email.pl b/contrib/bug_email.pl
index 98b8d157e..6844fa279 100755
--- a/contrib/bug_email.pl
+++ b/contrib/bug_email.pl
@@ -38,7 +38,7 @@
#
# You need to work with bug_email.pl the MIME::Parser installed.
#
-# $Id: bug_email.pl,v 1.29 2005/08/26 23:11:32 bugreport%peshkin.net Exp $
+# $Id: bug_email.pl,v 1.30 2005/11/25 19:47:38 timeless%mozdev.org Exp $
###############################################################
# 02/12/2000 (SML)
@@ -193,7 +193,7 @@ sub horLine( )
# Check if $Name is in $GroupName
# This is no more CreateBugs group, so I'm using this routine to just determine if the user is
-# in the database. Eventually, here should be a seperate routine or renamed, or something (SML)
+# in the database. Eventually, here should be a separate routine or renamed, or something (SML)
sub CheckPermissions {
my ($GroupName, $Name) = @_;
@@ -451,7 +451,7 @@ sub FetchAllSQLData( )
# 0 - Its an error, but bugzilla can process the bug. The user should
# handle that as a warning.
#
-# 1 - Its a real bug. Bugzilla cant store the bug. The mail has to be
+# 1 - It's a real bug. Bugzilla can't store the bug. The mail has to be
# resent.
#
# 2 - Permission error: The user does not have the permission to send
@@ -465,7 +465,7 @@ sub BugMailError($ $ )
{
my ( $errflag, $text ) = @_;
- # On permission error, dont sent all other Errors back -> just quit !
+ # On permission error, don't sent all other Errors back -> just quit !
if( $errflag == 2 ) { # Permission-Error
Reply( $SenderShort, $Message_ID, "Bugzilla Error", "Permission denied.\n\n" .
"You do not have the permissions to create a new bug. Sorry.\n" );
@@ -677,7 +677,7 @@ sub extractControls( $ )
}
}
- # thats it.
+ # that's it.
return( $backbody );
}
diff --git a/contrib/bugmail_help.html b/contrib/bugmail_help.html
index a2f89f260..1b43cd2b5 100644
--- a/contrib/bugmail_help.html
+++ b/contrib/bugmail_help.html
@@ -39,7 +39,7 @@ You receive a reply mail with the new bug-ID if your request was ok.
If not, you get a mail with
some help on the bugmail system and a specific analysis of your request.
<P>
-Please dont refuse to send one or two wrong mails, you will get all the information
+Please don't refuse to send one or two wrong mails, you will get all the information
you need in the replies, and <I>only</I> in the mail replies. The information on this
page, concerning available products, versions and so on, is not dynamicly generated and
may be old therefore.
@@ -91,23 +91,23 @@ hopefully valid value.
<TR>
<TD>@rep_platform</TD>
<TD>The desired platform</TD>
- <TD>no.<br>If you dont give a value, this field is set to <I>All</I>.</TD>
+ <TD>no.<br>If you don't give a value, this field is set to <I>All</I>.</TD>
</TR>
<TR>
<TD>@bug_severity</TD>
<TD>The severity of the bug</TD>
- <TD>no. <br> If you dont give a value, this field is set to
+ <TD>no. <br> If you don't give a value, this field is set to
<I>normal</I></TD>
</TR>
<TR>
<TD>@priority</TD>
<TD>The priority of the bug</TD>
- <TD>no.<br>If you dont give a value, this field is set to <I>P3</I></TD>
+ <TD>no.<br>If you don't give a value, this field is set to <I>P3</I></TD>
</TR>
<TR>
<TD>@op_sys</TD>
<TD>The operating system</TD>
- <TD>no.<br>If you dont give a value, this field is set to <I>Linux</I>.</TD>
+ <TD>no.<br>If you don't give a value, this field is set to <I>Linux</I>.</TD>
</TR>
<TR>
<TD>@assigned_to</TD>
@@ -150,7 +150,7 @@ Give string values for the most keys above. Some keywords require special value
<ol>
<li>E-Mail adresses: If you want to set the qa-contact, specify a email-adress for @qa_contact. The email must be known by bugzilla of course.</li>
<li>Listvalues: Most of the values have to be one of a list of valid values. Try by sending
-a mail and read the reply. Skip fields if you dont get help for them unless you dont know
+a mail and read the reply. Skip fields if you don't get help for them unless you don't know
which values you may choose.</li>
<li>free Text: The descriptions may be free text. </li>
<li>Special: The field groupset may be specified in different in three different kinds:
@@ -181,7 +181,7 @@ Some of the values must be choosen from a list:<br>
<p>
After you have specified the required keywords and maybe some other value, you may
-describe your bug. You dont need a keyword for starting your bug description. All
+describe your bug. You don't need a keyword for starting your bug description. All
text which follows the keyword block is handled as long description of the bug.
<p>
@@ -198,7 +198,7 @@ the attachment in bugzilla.
<H1><A NAME="examplemail">Example Mail</A></H1>
-See the example of the mail <b>body</b> (Dont forget to specify the short description
+See the example of the mail <b>body</b> (Don't forget to specify the short description
in the mail subject):<hr><pre>
@product = Bugzilla
diff --git a/contrib/gnatsparse/gnatsparse.py b/contrib/gnatsparse/gnatsparse.py
index b317b240d..5315ee8b0 100755
--- a/contrib/gnatsparse/gnatsparse.py
+++ b/contrib/gnatsparse/gnatsparse.py
@@ -270,7 +270,7 @@ def load_responsible(fname):
rfp.close()
def split_csl(list):
- """ Split a comma seperated list """
+ """ Split a comma separated list """
newlist = re.split(r"""\s*,\s*""", list)
return newlist
diff --git a/process_bug.cgi b/process_bug.cgi
index e56793fcd..77496f2a3 100755
--- a/process_bug.cgi
+++ b/process_bug.cgi
@@ -341,7 +341,7 @@ if (((defined $cgi->param('id') && $cgi->param('product') ne $oldproduct)
my %defaults;
# We set the defaults to these fields to the old value,
# if its a valid option, otherwise we use the default where
- # thats appropriate
+ # that's appropriate
$vars->{'versions'} = $::versions{$prod};
if ($vok) {
$defaults{'version'} = $cgi->param('version');