Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
bugzilla
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
etersoft
bugzilla
Commits
4accb195
Commit
4accb195
authored
Mar 19, 2002
by
timeless%mac.com
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Bug 106386 rid source of misspellings
r=db48x sr=blake a=asa
parent
838fdab5
Hide whitespace changes
Inline
Side-by-side
Showing
6 changed files
with
8 additions
and
8 deletions
+8
-8
Bugzilla-Guide.html
docs/html/Bugzilla-Guide.html
+2
-2
bzhacking.html
docs/html/bzhacking.html
+1
-1
patches.sgml
docs/sgml/patches.sgml
+1
-1
Bugzilla-Guide.txt
docs/txt/Bugzilla-Guide.txt
+2
-2
patches.xml
docs/xml/patches.xml
+1
-1
queryhelp.cgi
queryhelp.cgi
+1
-1
No files found.
docs/html/Bugzilla-Guide.html
View file @
4accb195
...
@@ -7419,7 +7419,7 @@ CLASS="function"
...
@@ -7419,7 +7419,7 @@ CLASS="function"
>
when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting
<TT
>
when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than aribtrarily putting
<TT
CLASS=
"function"
CLASS=
"function"
>
binmode()
</TT
>
binmode()
</TT
>
at the begining of the attachment files, there should be logic to determine if
<TT
>
at the begin
n
ing of the attachment files, there should be logic to determine if
<TT
CLASS=
"function"
CLASS=
"function"
>
binmode()
</TT
>
binmode()
</TT
>
is needed or not.
>
is needed or not.
...
@@ -16369,7 +16369,7 @@ CLASS="command"
...
@@ -16369,7 +16369,7 @@ CLASS="command"
>
Whitespace
>
Whitespace
</P
</P
><P
><P
>
Bugzilla's prefered indentation is 4 spaces (no tabs, please).
>
Bugzilla's prefer
r
ed indentation is 4 spaces (no tabs, please).
</P
</P
></LI
></LI
><LI
><LI
...
...
docs/html/bzhacking.html
View file @
4accb195
...
@@ -217,7 +217,7 @@ CLASS="command"
...
@@ -217,7 +217,7 @@ CLASS="command"
>
Whitespace
>
Whitespace
</P
</P
><P
><P
>
Bugzilla's prefered indentation is 4 spaces (no tabs, please).
>
Bugzilla's prefer
r
ed indentation is 4 spaces (no tabs, please).
</P
</P
></LI
></LI
><LI
><LI
...
...
docs/sgml/patches.sgml
View file @
4accb195
...
@@ -317,7 +317,7 @@ grep (/$value/, @array);
...
@@ -317,7 +317,7 @@ grep (/$value/, @array);
Whitespace
Whitespace
</para>
</para>
<para>
<para>
Bugzilla's prefered indentation is 4 spaces (no tabs, please).
Bugzilla's prefer
r
ed indentation is 4 spaces (no tabs, please).
</para>
</para>
</listitem>
</listitem>
<listitem>
<listitem>
...
...
docs/txt/Bugzilla-Guide.txt
View file @
4accb195
...
@@ -2171,7 +2171,7 @@ binmode(STDOUT);
...
@@ -2171,7 +2171,7 @@ binmode(STDOUT);
According to bug 62000, the perl documentation says that you should
According to bug 62000, the perl documentation says that you should
always use binmode() when dealing with binary files, but never when
always use binmode() when dealing with binary files, but never when
dealing with text files. That seems to suggest that rather than
dealing with text files. That seems to suggest that rather than
aribtrarily putting binmode() at the begining of the attachment files,
aribtrarily putting binmode() at the begin
n
ing of the attachment files,
there should be logic to determine if binmode() is needed or not.
there should be logic to determine if binmode() is needed or not.
Tip
Tip
...
@@ -5921,7 +5921,7 @@ D.5.2. Coding Style for Bugzilla
...
@@ -5921,7 +5921,7 @@ D.5.2. Coding Style for Bugzilla
Bugzilla.
Bugzilla.
* Whitespace
* Whitespace
Bugzilla's prefered indentation is 4 spaces (no tabs, please).
Bugzilla's prefer
r
ed indentation is 4 spaces (no tabs, please).
* Curly braces.
* Curly braces.
The opening brace of a block should be on the same line as the
The opening brace of a block should be on the same line as the
statement that is causing the block and the closing brace should
statement that is causing the block and the closing brace should
...
...
docs/xml/patches.xml
View file @
4accb195
...
@@ -317,7 +317,7 @@ grep (/$value/, @array);
...
@@ -317,7 +317,7 @@ grep (/$value/, @array);
Whitespace
Whitespace
</para>
</para>
<para>
<para>
Bugzilla's prefered indentation is 4 spaces (no tabs, please).
Bugzilla's prefer
r
ed indentation is 4 spaces (no tabs, please).
</para>
</para>
</listitem>
</listitem>
<listitem>
<listitem>
...
...
queryhelp.cgi
View file @
4accb195
...
@@ -575,7 +575,7 @@ find describe. Selecting one or more of the products, versions, components, or m
...
@@ -575,7 +575,7 @@ find describe. Selecting one or more of the products, versions, components, or m
<h4>Products</h4>
<h4>Products</h4>
<p>Although all subprojects within the Mozilla project are simil
i
ar, there are several seperate
<p>Although all subprojects within the Mozilla project are similar, there are several seperate
products being developed. Each product has its own components.
products being developed. Each product has its own components.
}
;
}
;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment