New comment

Name:
Email:
Homepage:
Location:
JavaScript support is required for this form to work.
Calculate:	31 plus 2 equals
Subject:
Entry text: [quote="Justin Wood (Callek)"]With regard to hg history, I think we should import history from the original mozilla-central Hg import date (there is a cvs tag for it) and use the importer script (which will need some changes to work for us). Then when we are ready to switch primary dev to 1.9.1 we can "close" the CVS tree for whatever we import to Hg. And in between we can do periodic imports from CVS for those directories, (we can keep it all on a cvs-mailsuite-mirror repo or some such). When we make the change we could/should tag the tip changeset as "Moved dev to 1.9.1"..., well a tag that could mean that. That will make history keeping quite well. If Thunderbird and SeaMonkey wish to make the official switch seperately we can require CVS landings for that project and use the mirror-importer longer, merge conflicts should be easily rectified in such a case. Re: extensions It might make sense for an --enable-app-extensions=... flag that looks for a "app"/"extensions"/[extension] for each extension, and could have a "app"/"extensions"/list of some sort, with markings for "default" and for "all" Might even make sense to have it as part of normal build system for said list and the real extensions dir could keep that (with IFDEFs maybe to do away with current configure rules)[/quote]
I accept and follow the policy of Home of KaiRo.

This entry supports emoji, bbCode, and some HTML codes.