You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by jteh on 2015-02-16 03:51
Currently, we are converting t2t files for all languages on every commit with a t2t file (regardless of language). It'd be better if we only converted the t2t files for the languages for which t2t files were modified. This should be a fairly simple matter of using convertOne.sh instead of convertT2t.sh for the appropriate languages, just as we do for poChecker. Blocking #4945
The text was updated successfully, but these errors were encountered:
Comment 1 by jteh on 2015-02-18 06:21
Better still, we should report any errors in the commit message, rather than sending a separate email for encoding errors. Currently, unless I'm missing something, we don't send anything at all for key commands generation errors.
Comment 6 by jteh on 2015-02-25 05:26
I think I'm pretty much done with this. I implemented #4945 as part of this. However, I will be offline for a few weeks any time now, so I'll probably hold off on committing it until after I get back in case anything breaks.
Reported by jteh on 2015-02-16 03:51
Currently, we are converting t2t files for all languages on every commit with a t2t file (regardless of language). It'd be better if we only converted the t2t files for the languages for which t2t files were modified. This should be a fairly simple matter of using convertOne.sh instead of convertT2t.sh for the appropriate languages, just as we do for poChecker.
Blocking #4945
The text was updated successfully, but these errors were encountered: