Re: Can we start using C++ STL containers in Mozilla code?
On 12/10/2013 16:17, Joshua Cranmer wrote: I think the right answer is to make the myriad of datatypes we have more STL-ish--as a first step at least, can we at least add iterator support for them and get rid of the abominable EnumerateForwards/EnumerateBackewards methods? This would allow us to use range-based for once our minimum compiler support gets there. Yes please. From what i saw so far we even have a bunch different iteration approaches with the current Mozilla containers. We also seem to have a lot of algorithmic duplication which seems pretty bad for maintenance etc. - getting all, or most, containers to implement compatible interfaces would allow for future improvements and cleanups. Georg ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: PSA: Shutting down my mozilla git mirror in three weeks
I just finished this work. https://github.com/mozilla/mozilla-central will not be updated any more, and I will replace its content with a short notice explaining the situation on Monday. Cheers, -- Ehsan http://ehsanakhgari.org/ On Wed, Dec 11, 2013 at 2:46 PM, Ehsan Akhgari ehsan.akhg...@gmail.comwrote: Here's another reminder everyone. This is happening *this Friday* at 1pm, EST. I will shut down my update scripts on Friday, and will push a non-fast-forward commit to all of the branches on that repo on Monday so that people who do not see this message before that time would have a way of knowing about this change. If you haven't done already, *please* take a few minutes to do this right now. If you hit problems, please ping me over email or IRC, or hop on #git. Thanks! -- Ehsan http://ehsanakhgari.org/ On Mon, Dec 9, 2013 at 2:12 PM, Ehsan Akhgari ehsan.akhg...@gmail.comwrote: Gentle reminder that this is happening this Friday. Ideally you should have migrated your local git clones to the new repositories by now, but if you haven't, please take some time to do this before this Friday. Again, if you have a reason why I should postpone this please speak up! Cheers, -- Ehsan http://ehsanakhgari.org/ On Mon, Nov 25, 2013 at 7:39 AM, Ehsan Akhgari ehsan.akhg...@gmail.comwrote: Dear all, For the past two and a half years I have been maintaining a git mirror of mozilla-central plus a lot of the other branches that people found useful at https://github.com/mozilla/mozilla-central. Over the years this proved to be too much work for me to keep up with, and given the existence of the new git mirrors that are supported by RelEng, I'm planning to shut down the update jobs for this repository on Friday, Dec 13, 2013 and take the repository down. I strongly suggest that if you have been using and relying on this repository before, please consider switching to the RelEng repositories as soon as possible. https://github.com/mozilla/gecko-dev is the main repository where you can find branches such as trunk/aurora/b2g branches/etc and https://github.com/mozilla/gecko-projects is a repository which contains project branches and twigs. (Note that my repository hosts all of these branches in a single location, but from now on if you use both of these branch subsets you will need to have two upstream remotes added in your local git clone.) The RelEng repositories have a similar history line including the CVS history but they have completely different commit SHA1s, so pulling that repo into your existing clones is probably not what you want. If you don't have a lot of non-merged branches, your safest bet is cloning from scratch and then port your existing branches manually. If you have a lot of local branches, you may want to wait for the script that John Schoenick is working on in bug 929338 which will assist you in rebasing those branches on top of the new history line. Last but not least, I really hate to have to disrupt your workflow like this. I do hope that three weeks is enough advance notice for everybody to successfully switch over to the new mirrors, but if you have a reason for me to delay this please let me know and I will do my best to accommodate. Cheers, -- Ehsan http://ehsanakhgari.org/ ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Valgrind-on-TBPL
On Wed, Dec 4, 2013 at 12:02 PM, Nicholas Nethercote n.netherc...@gmail.com wrote: I'm working on getting Valgrind (Linux64-only) runs visible on TBPL. https://bugzilla.mozilla.org/show_bug.cgi?id=valgrind-green is the tracking bug. [...] 5) Easily run on try server catlee got Valgrind jobs running on try in bug 946005. They are running in |-p all| try runs, though you need to append |showall=1| to the URL to see them because they're hidden by default. And you can use |-p linux64-valgrind| to choose the Valgrind build specifically. Bug 950223 is open to update trychooser. More generally, there's been great progress on all the required steps, and it's been much faster than I expected. Special thanks to catlee for doing all the required changes on the releng side. The remaining tasks all look fairly straightforward. Nick ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Rendering meeting, Monday 2;30pm PDT (the earlier time)
The Rendering meeting is about all things Gfx, Image, Layout, and Media. It takes place every second Monday, alternating between 2:30pm PDT and 5:30pm PDT. The next meeting will take this coming Monday, December 16th at 2:30 PM US/Pacific Please add to the agenda: https://wiki.mozilla.org/Platform/GFX/ 2013-December-16#Agenda San Francisco - Monday, 2:30pm Winnipeg - Monday, 4:30pm Toronto - Monday, 5:30pm GMT/UTC - Monday, 22:30 Paris - Monday, 11:30pm Taipei - Tuesday, 6:30am Brisbane - Tuesday, 8:30am Auckland - Tuesday, 11:30am Video conferencing: Vidyo room Graphics (9366) https://v.mozilla.com/flex.html?roomdirect.htmlkey=FILzKzPcA6W2 Phone conferencing: +1 650 903 0800 x92 Conf# 99366 +1 416 848 3114 x92 Conf# 99366 +1 800 707 2533 (pin 369) Conf# 99366 -- - Milan ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
W3C Proposed Recommendations: Performance Timeline, User Timing, JSON-LD
W3C recently published the following proposed recommendation (the stage before W3C's final stage, Recommendation): http://www.w3.org/TR/cors/ Cross-Origin Resource Sharing (CORS) There's a call for review to W3C member companies (of which Mozilla is one) open until January 14. If there are comments you think Mozilla should send as part of the review, or if you think Mozilla should voice support or opposition to the specification, please say so in this thread. (I'd note, however, that there have been many previous opportunities to make comments, so it's somewhat bad form to bring up fundamental issues for the first time at this stage.) -David -- 턞 L. David Baron http://dbaron.org/ 턂 턢 Mozilla https://www.mozilla.org/ 턂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914) ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: (un)safety of NS_LITERAL_STRING(...).get()
L. David Baron wrote: const PRUnichar *comma = MOZ_UTF16(,); In the case addressed by the referenced bug, the string was used in a call to Append, which meant that this is still inefficient. The patch in the bug fixed this by switching to appending a character rather than a string. If you do need to append a wide string rather than a character you have the choice of s.Append(NS_LITERAL_STRING(stuff)) or s.AppendLiteral(stuff), both of which measure the length of the string at compile time, unlike s.Append(MOZ_UTF16(stuff)) which measures it at run time. As of bug 514173 I hope to make s.AppendLiteral(MOZ_UTF16(stuff)) work too. (I can't overload Append because I can't guarantee that you're really passing a literal.) -- Warning: May contain traces of nuts. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: PSA: Shutting down my mozilla git mirror in three weeks
Similarly, the sync processes for these four repos have been stopped, and we'll replace their content on Monday. On 12/11/13 4:25 PM, Aki Sasaki wrote: I think it also makes sense to use this same timeframe for EOLing the following experimental repos: https://github.com/mozilla/releases-mozilla-central https://github.com/mozilla/releases-mozilla-aurora https://github.com/mozilla/releases-mozilla-beta https://github.com/mozilla/releases-mozilla-release These introduced a 3rd set of SHAs, and the above branches are supported in gecko-dev. I don't know of anyone who relies on these. Please let me know if you do rely on these and can't make the switch to gecko-dev in time. On 12/11/13 11:46 AM, Ehsan Akhgari wrote: Here's another reminder everyone. This is happening *this Friday* at 1pm, EST. I will shut down my update scripts on Friday, and will push a non-fast-forward commit to all of the branches on that repo on Monday so that people who do not see this message before that time would have a way of knowing about this change. If you haven't done already, *please* take a few minutes to do this right now. If you hit problems, please ping me over email or IRC, or hop on #git. Thanks! -- Ehsan http://ehsanakhgari.org/ On Mon, Dec 9, 2013 at 2:12 PM, Ehsan Akhgari ehsan.akhg...@gmail.comwrote: Gentle reminder that this is happening this Friday. Ideally you should have migrated your local git clones to the new repositories by now, but if you haven't, please take some time to do this before this Friday. Again, if you have a reason why I should postpone this please speak up! Cheers, -- Ehsan http://ehsanakhgari.org/ On Mon, Nov 25, 2013 at 7:39 AM, Ehsan Akhgari ehsan.akhg...@gmail.comwrote: Dear all, For the past two and a half years I have been maintaining a git mirror of mozilla-central plus a lot of the other branches that people found useful at https://github.com/mozilla/mozilla-central. Over the years this proved to be too much work for me to keep up with, and given the existence of the new git mirrors that are supported by RelEng, I'm planning to shut down the update jobs for this repository on Friday, Dec 13, 2013 and take the repository down. I strongly suggest that if you have been using and relying on this repository before, please consider switching to the RelEng repositories as soon as possible. https://github.com/mozilla/gecko-dev is the main repository where you can find branches such as trunk/aurora/b2g branches/etc and https://github.com/mozilla/gecko-projects is a repository which contains project branches and twigs. (Note that my repository hosts all of these branches in a single location, but from now on if you use both of these branch subsets you will need to have two upstream remotes added in your local git clone.) The RelEng repositories have a similar history line including the CVS history but they have completely different commit SHA1s, so pulling that repo into your existing clones is probably not what you want. If you don't have a lot of non-merged branches, your safest bet is cloning from scratch and then port your existing branches manually. If you have a lot of local branches, you may want to wait for the script that John Schoenick is working on in bug 929338 which will assist you in rebasing those branches on top of the new history line. Last but not least, I really hate to have to disrupt your workflow like this. I do hope that three weeks is enough advance notice for everybody to successfully switch over to the new mirrors, but if you have a reason for me to delay this please let me know and I will do my best to accommodate. Cheers, -- Ehsan http://ehsanakhgari.org/ ___ dev-planning mailing list dev-plann...@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-planning ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
W3C Proposed Recommendation: CORS
[ resending with correct subject line ] W3C recently published the following proposed recommendation (the stage before W3C's final stage, Recommendation): http://www.w3.org/TR/cors/ Cross-Origin Resource Sharing (CORS) There's a call for review to W3C member companies (of which Mozilla is one) open until January 14. If there are comments you think Mozilla should send as part of the review, or if you think Mozilla should voice support or opposition to the specification, please say so in this thread. (I'd note, however, that there have been many previous opportunities to make comments, so it's somewhat bad form to bring up fundamental issues for the first time at this stage.) -David -- 턞 L. David Baron http://dbaron.org/ 턂 턢 Mozilla https://www.mozilla.org/ 턂 Before I built a wall I'd ask to know What I was walling in or walling out, And to whom I was like to give offense. - Robert Frost, Mending Wall (1914) signature.asc Description: Digital signature ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: PSA: Shutting down my mozilla git mirror in three weeks
Ehsan, I'm sure I'm speaking for many Mozillians when I say thank you for running this service - from building on Chris Double's initial work, keeping it running while dealing with GitHub shenanigans, and for assisting with a transition plan to its natural successor. You could easily have done nothing, but you stepped up and enabled countless people to access the Firefox source code on their terms. If that's not worthy of spamming dev-planning for, I don't know what is. Thanks again, Gregory On Dec 14, 2013, at 5:28, Ehsan Akhgari ehsan.akhg...@gmail.com wrote: I just finished this work. https://github.com/mozilla/mozilla-central will not be updated any more, and I will replace its content with a short notice explaining the situation on Monday. Cheers, -- Ehsan http://ehsanakhgari.org/ On Wed, Dec 11, 2013 at 2:46 PM, Ehsan Akhgari ehsan.akhg...@gmail.com wrote: Here's another reminder everyone. This is happening *this Friday* at 1pm, EST. I will shut down my update scripts on Friday, and will push a non-fast-forward commit to all of the branches on that repo on Monday so that people who do not see this message before that time would have a way of knowing about this change. If you haven't done already, *please* take a few minutes to do this right now. If you hit problems, please ping me over email or IRC, or hop on #git. Thanks! -- Ehsan http://ehsanakhgari.org/ On Mon, Dec 9, 2013 at 2:12 PM, Ehsan Akhgari ehsan.akhg...@gmail.com wrote: Gentle reminder that this is happening this Friday. Ideally you should have migrated your local git clones to the new repositories by now, but if you haven't, please take some time to do this before this Friday. Again, if you have a reason why I should postpone this please speak up! Cheers, -- Ehsan http://ehsanakhgari.org/ On Mon, Nov 25, 2013 at 7:39 AM, Ehsan Akhgari ehsan.akhg...@gmail.com wrote: Dear all, For the past two and a half years I have been maintaining a git mirror of mozilla-central plus a lot of the other branches that people found useful at https://github.com/mozilla/mozilla-central. Over the years this proved to be too much work for me to keep up with, and given the existence of the new git mirrors that are supported by RelEng, I'm planning to shut down the update jobs for this repository on Friday, Dec 13, 2013 and take the repository down. I strongly suggest that if you have been using and relying on this repository before, please consider switching to the RelEng repositories as soon as possible. https://github.com/mozilla/gecko-dev is the main repository where you can find branches such as trunk/aurora/b2g branches/etc and https://github.com/mozilla/gecko-projects is a repository which contains project branches and twigs. (Note that my repository hosts all of these branches in a single location, but from now on if you use both of these branch subsets you will need to have two upstream remotes added in your local git clone.) The RelEng repositories have a similar history line including the CVS history but they have completely different commit SHA1s, so pulling that repo into your existing clones is probably not what you want. If you don't have a lot of non-merged branches, your safest bet is cloning from scratch and then port your existing branches manually. If you have a lot of local branches, you may want to wait for the script that John Schoenick is working on in bug 929338 which will assist you in rebasing those branches on top of the new history line. Last but not least, I really hate to have to disrupt your workflow like this. I do hope that three weeks is enough advance notice for everybody to successfully switch over to the new mirrors, but if you have a reason for me to delay this please let me know and I will do my best to accommodate. Cheers, -- Ehsan http://ehsanakhgari.org/ ___ firefox-dev mailing list firefox-...@mozilla.org https://mail.mozilla.org/listinfo/firefox-dev ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
