Closed
Bug 143165
Opened 23 years ago
Closed 23 years ago
client.mk ignores MOZ_CO_DATE for client.mk and modules.mk
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ajschult784, Assigned: netscape)
Details
Attachments
(1 file)
|
792 bytes,
patch
|
leaf
:
review+
|
Details | Diff | Splinter Review |
Specifying MOZ_CO_DATE in client.mk (or in .mozconfig) doesn't work. client.mk
pulls the current versions of client.mk and build/unix/modules.mk rather than
the ones corresponding to MOZ_CO_DATE.
|
Reporter | |
Comment 1•23 years ago
|
||
|
Assignee | |
Comment 2•23 years ago
|
||
Ignoring MOZ_CO_DATE for client.mk was intentional. It allowed us to fix date
pulling issues with client.mk on tinderboxes w/o having to go touch each
tinderbox. Leaf, do we still need that feature?
|
|
Reporter | |
Comment 3•23 years ago
|
||
MOZ_CO_DATE gives me a fool-proof (me=fool) way to find regressions and/or pull
sources older than those available as tarballs.
|
|
||
Comment 4•23 years ago
|
||
Comment on attachment 82874 [details] [diff] [review]
patch to pull client.mk and modules.mk based on date
wow. i can't believe it's not butter.
Attachment #82874 -
Flags: review+
|
|
Assignee | |
Comment 5•23 years ago
|
||
Parkay!
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
|
||
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•