Closed Bug 90520 Opened 24 years ago Closed 24 years ago

^M in nsSecureBrowserUIImpl.cpp:340 breaks IRIX build

Categories

(Core Graveyard :: Security: UI, defect)

1.0 Branch
SGI
IRIX
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: mcafee, Assigned: ddrinan0264)

References

()

Details

windows CRLF ^M in mozilla/security/manager/ssl/srcnsSecureBrowserUIImpl.cpp:340 breaks IRIX build, this was accidentally checked in as part of the 1.19 checkin for this file.
OS: Linux → IRIX
Hardware: PC → SGI
How does one avoid checking in ^M's? Is cvs commit supposed to strip them out automatically?
Component: Security: General → Security: Crypto
QA Contact: ckritzer → junruh
using wincvs on windows, or making sure not to have them already when committing from unix (dos2unix [if avail] will remove them, as can various other things in emacs, perl, sed, vi) but what would really help is if people would report correct cvs paths. (arg!) http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/security/manager/ssl/src/ns SecureBrowserUIImpl.cpp&rev=1.19&mark=340#340 Is there a reason this bug is still open? 1.20 ddrinan%netscape.com Jul 12 11:44 Remove ^M that was accidentially checked in. It's a good thing people don't care that we misspell checkin comments (i did it yesterday or the day before), >accidentally< this problem is no longer the reason for irix being red.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Verified per timeless' comment.
Status: RESOLVED → VERIFIED
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Mass changing Security:Crypto to PSM
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.