On Fri, May 24, 2013 at 4:33 PM, Benoit Jacob wrote:
> I also thought that it was obvious that a suitably chosen subset of TeX
> could be free of such unwanted characteristics.
So basically that would involve inventing something new that currently
does not exist and are currently isn't supported
This is only tangentially on topic, but I have a git pre-commit hook
which detects .orig files and trailing whitespace. It's saved me a
lot of embarrassment.
I also have a git tool which will fix trailing whitespace in your patch.
https://github.com/jlebar/moz-git-tools#pre-commit
https://github
On 25/05/13 04:16, Ehsan Akhgari wrote:
> On 2013-05-24 11:46 AM, Benoit Girard wrote:
> Another option is to use clang-format, which can lexically parse diff
> files.
A pre-upload check would give the fastest feedback.
It would help me (and those who review my code) if there is an easy way
to ch
Meeting Details:
* Agenda: https://wiki.mozilla.org/WebAPI/2013-05-28
* WebAPI Vidyo room
* A room we can find, San Francisco office
* Spadina conf. room, Toronto office
* Allo Allo conf. room, London office
* Vidyo Phone # +1-650-903-0800 x92 Conference #98413 (US/INTL)
* US Vidyo Phone # 1-800
The alternative is to use C++ workers. This doesn't work for addons
obviously, but those aren't yet a concern for B2G.
Weren't we moving addons into separate processes anyway?
/ Jonas
On May 24, 2013 12:39 AM, "David Rajchenbach-Teller"
wrote:
> Well, if we do not want the main thread to collap
5 matches
Mail list logo