Closed Bug 334877 Opened 18 years ago Closed 18 years ago
move non-prefwindow xpfe/components chrome to suite/
20.13 KB, patch
|Details | Diff | Splinter Review
3.75 KB, text/plain
After prefwindow chrome is moved to suite/ by bug 333383, I'll do the move of the rest of xpfe/components chrome here
Here's the jar.mn part of this, all remaining communicator chrome of xpofe/components gets moved to suite/ - with the exception of the old alerts and update services, which are obsoleted by suiterunner anyways. Even though the moved files are used by both old xpfe-based suite and suiterunner, it probably makes little sense to move files that are obviously killed soon anyways. The patch is against files already changed by bug bug 333383 already, so that only differences to that are shown. The cvsmoves file is coming up soon.
Those are the files that need to be moved/copied - again, I'll open a cvs moves bug once I got reviews so I know the new locations of those files are correct.
While generating the next cvsmoves file, I realized I used locales/chrome here instead of locales/en-US/chrome - sorry!
This has suffered bitrot due to various other checkins (mainly my own ones), here's an un-bitrotted version (and real cvs diff now, as the prefwindow move is already in).
Comment on attachment 219327 [details] [diff] [review] cvsmoves for communicator components chrome This file has a small glitch in the directory.dtd line, I'll attach a corrected version to the cvs copy bug.
Attachment #219327 - Attachment is obsolete: true
Comment on attachment 222401 [details] [diff] [review] jar.mn changes for moving relevant components chrome, unbitrotted Checked in. Leaving this open until I'm sure it works and I have cvs removed those files that are unused after that step.
This is the list of files that were obsoleted by this bug, and were cvs removed a moment ago.
FIXED, finally ;-)
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.