If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Move protocol handler howto to correct directory

VERIFIED FIXED

Status

Developer Documentation
General
P3
normal
VERIFIED FIXED
18 years ago
5 years ago

People

(Reporter: old account, Assigned: Brian Ryner (not reading))

Tracking

Details

(Reporter)

Description

18 years ago
The proto handler howto needs to be moved to the new netwerk doc directory
(currently it's in with the old netlib documentation).
(Reporter)

Updated

18 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 1

18 years ago
Moving all my bugs to this email.
Assignee: bryner → bryner
Status: ASSIGNED → NEW
(Assignee)

Updated

18 years ago
Status: NEW → ASSIGNED

Comment 2

18 years ago
*spam* changing qa contact from nobody@mozilla.org to me (BlakeR1234@aol.com) 
on 121 open or resolved (but not verified) bugs.  sorry for the spam everybody, 
but most of these bugs would just remain dormant and not checked by QA 
otherwise.  I'm not sure how so many bugs have nobody as their QA contact, but 
I suspect this is the fault of some sort of bugzilla corruption that happened 
at some point (most of these bugs are in the 20000-26000 range, and I don't see 
where in the activity log that QA contact explicitly changed to 
nobody@mozilla.org)

Anyways, sorry again for spam.  If you really get annoyed, I'm usually 
available in #mozilla on IRC for torture.
QA Contact: nobody → BlakeR1234
(Assignee)

Comment 3

17 years ago
I was bored, so I took care of this.  The protocol handler howto is now at:

http://www.mozilla.org/projects/netlib/new-handler.html
Status: ASSIGNED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED

Comment 4

17 years ago
vrfy
Status: RESOLVED → VERIFIED
Component: Mozilla Developer → Documentation Requests
Product: Documentation → Mozilla Developer Center
Component: Documentation Requests → Documentation
Product: Mozilla Developer Network → Mozilla Developer Network
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
You need to log in before you can comment on or make changes to this bug.