Closed Bug 602754 Opened 14 years ago Closed 14 years ago

Fix "a the" in comments (for NSS code)

Categories

(NSS :: Libraries, defect)

x86
All
defect
Not set
trivial

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ewong, Assigned: ewong)

References

Details

Attachments

(1 file, 1 obsolete file)

security/nss/cmd/symkeyutil/symkey.man (View Hg log or Hg annotations)
    * line 30 -- -L takes the standard set of options. It lists all the keys in a the

security/nss/lib/softoken/legacydb/lowkeyi.h (View Hg log or Hg annotations)
    * line 99 -- ** "f" is a the callback function for getting the password

security/nss/lib/smime/smime.h (View Hg log or Hg annotations)
    * line 86 -- * XXX This is for a the current module, I think, so local, static storage

security/nss/lib/pk11wrap/pk11akey.c (View Hg log or Hg annotations)
    * line 275 -- * We need this so we can reliably determine if a the ecPoint passed to us

security/nss/lib/pk11wrap/pk11pbe.c (View Hg log or Hg annotations)
    * line 1447 -- * get a the crypto mechanism directly from the pbe algorithmid.

security/nss/lib/pkcs7/secmime.h (View Hg log or Hg annotations)
    * line 92 -- * XXX This is for a the current module, I think, so local, static storage

security/nss/lib/sqlite/sqlite3.c (View Hg log or Hg annotations)
    * line 80795 -- ** If regPrev>0 then it is a the first register in a vector that
    * line 100815 -- ** to by the argument to point a the "simple" tokenizer implementation.

security/nss/lib/jar/jarver.c (View Hg log or Hg annotations)
    * line 127 -- /* fill in the path, if supplied. This is a the location
Assignee: nobody → ewong
Blocks: 452636
Status: NEW → ASSIGNED
(In reply to comment #0)

> security/nss/lib/sqlite/sqlite3.c (View Hg log or Hg annotations)
>     * line 80795 -- ** If regPrev>0 then it is a the first register in a vector

Not part of the bug.  Was included by mistake.  This should be for bug #602770.
Attached patch Fix ' a the ' in NSS code. (obsolete) — Splinter Review
Attachment #481999 - Flags: review?
Attachment #481999 - Flags: review? → review?(wtc)
Attachment #481999 - Flags: review?(wtc) → review+
Added the bug # to the comment.
Attachment #482004 - Flags: review?(wtc)
Attachment #481999 - Attachment is obsolete: true
Attachment #482004 - Flags: review?(wtc) → review+
Keywords: checkin-needed
Comment on attachment 482004 [details] [diff] [review]
Fix ' a the ' in NSS code.

Edmond, this patch needs to be reviewed and approved by an NSS team member.
Attachment #482004 - Flags: review+ → review?
Further, this contains a change to code inside the FIPS boundary.
Severity: normal → trivial
Target Milestone: --- → 3.13
(In reply to comment #4)
> Comment on attachment 482004 [details] [diff] [review]
> Fix ' a the ' in NSS code.
> 
> Edmond, this patch needs to be reviewed and approved by an NSS team member.

Sorry.  I made a mistake in setting up the checkin-needed and review+.  This
was supposed to be for a different bug.
(In reply to comment #5)
> Further, this contains a change to code inside the FIPS boundary.


My first patch was reviewed by wtc.  My second patch is a change in the bug header.
Attachment #482004 - Flags: review? → review?(nelson)
Edmund: thank you for the patch.  In the future, please do not create patches that do nothing but fix spelling errors or typos, unless the spelling errors or typos cause confusion.  I stated the rationale in bug 577267 comment 1, reproduced here for your convenience:

  Correcting misspellings that that most people have no trouble
  understanding (such as receive vs. recieve and existence vs.
  existance) adds noise to source code diffs, which can hurt
  a programmer's ability to spot the important changes.

  This is why I marked this bug WONTFIX.  However, it is fine
  to correct misspellings when you fix a bug or if the
  misspellings may cause misunderstanding.

I made an exception this time because you've written
the patch before being told about this.

Patch checked in on the NSS trunk (NSS 3.13).

Checking in cmd/symkeyutil/symkey.man;
/cvsroot/mozilla/security/nss/cmd/symkeyutil/symkey.man,v  <--  symkey.man
new revision: 1.3; previous revision: 1.2
done
Checking in lib/jar/jarver.c;
/cvsroot/mozilla/security/nss/lib/jar/jarver.c,v  <--  jarver.c
new revision: 1.20; previous revision: 1.19
done
Checking in lib/pk11wrap/pk11akey.c;
/cvsroot/mozilla/security/nss/lib/pk11wrap/pk11akey.c,v  <--  pk11akey.c
new revision: 1.32; previous revision: 1.31
done
Checking in lib/pk11wrap/pk11pbe.c;
/cvsroot/mozilla/security/nss/lib/pk11wrap/pk11pbe.c,v  <--  pk11pbe.c
new revision: 1.24; previous revision: 1.23
done
Checking in lib/smime/smime.h;
/cvsroot/mozilla/security/nss/lib/smime/smime.h,v  <--  smime.h
new revision: 1.9; previous revision: 1.8
done
Checking in lib/softoken/legacydb/lowkeyi.h;
/cvsroot/mozilla/security/nss/lib/softoken/legacydb/lowkeyi.h,v  <--  lowkeyi.h
new revision: 1.4; previous revision: 1.3
done
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Attachment #482004 - Flags: review?(nelson) → review+
(In reply to comment #8)
> Edmund: thank you for the patch.  In the future, please do not create patches
> that do nothing but fix spelling errors or typos, unless the spelling errors or
> typos cause confusion.  I stated the rationale in bug 577267 comment 1,
> reproduced here for your convenience:

Thanks, I will definitely keep this in mind.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: