include the correct tag to pull classic source, in classic build documents.

VERIFIED FIXED

Status

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

People

(Reporter: Daniel (Leaf) Nunes, Assigned: zach)

Tracking

Details

(URL)

(Reporter)

Description

18 years ago
"I wanted to grab mozilla classic to try and revive some old code, but I don't
remember the cvs tag and module
name. Do you remember? (You might want to put it on
http://www.mozilla.org/classic/build/classic-win.html
which really doesn't tell you this part). Thanks, Warren"
(Reporter)

Comment 1

18 years ago
when i'm back near my source tree, i'll fix this.
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

Comment 3

17 years ago
Adding classic keyword.
Keywords: classic
(Reporter)

Comment 4

17 years ago
jan, i think you have the wrong kind of classic here. this is not the classic
skin; removing keyword.
Keywords: classic

Updated

17 years ago
QA Contact: blakeross → nobody

Updated

17 years ago
QA Contact: nobody → david
(Assignee)

Comment 5

17 years ago
I can do this, but what is the tag?
(Reporter)

Updated

17 years ago
Assignee: leaf → zach
Status: ASSIGNED → NEW
(Reporter)

Comment 6

17 years ago
 
There are two tag choices... the branch is obviously the better one for actually 
doing work, since it can be changed:
       MozillaSourceClassic_19981026_BRANCH
       MozillaSourceClassic_19981026_BASE

Comment 7

16 years ago
accepting QA for mozilla developer docs.

some of these bugs have been around for a _long_ time. Reporters, would you
please review the bugs, see if the issues have been resolved, and close bugs
appropriately.

I will do a full review of all bugs not touched in one week (8th April). 

Thanks.

</spam>
QA Contact: mozilla → imajes
(Assignee)

Comment 8

15 years ago
Fixed, my checkin comment got way off (mozilla auto-fill filled in the checkin
comment from my last use of doctor :(, but this should do it. I took out the
reference to getting classic source from FTP monthly, we don't do that any more :)
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED

Comment 9

15 years ago
v
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.