Uh oh!
There was an error while loading. Please reload this page.
Simplify message paths - #108682
Conversation
rustbot
commented
Mar 2, 2023
Some changes occurred in compiler/rustc_codegen_gcc cc @antoyo
|
bors
commented
Mar 3, 2023
☔ The latest upstream changes (presumably #108707) made this pull request unmergeable. Please resolve the merge conflicts. |
bors
commented
Mar 8, 2023
☔ The latest upstream changes (presumably #108877) made this pull request unmergeable. Please resolve the merge conflicts. |
davidtwco
commented
Mar 8, 2023
@bors delegate=est31 Feel free to approve this after you rebase, it's likely to be a bit conflict prone. |
bors
commented
Mar 8, 2023
✌️ @est31 can now approve this pull request |
It's strange that github/bors shows this as a merge conflict as local rebasing works well without requiring merge conflict resolution... |
compiler-errors
commented
Mar 8, 2023
Yeah, sometimes that happens. I think bors's merge conflict resolution is a bit pessimistic? |
est31
commented
Mar 8, 2023
@bors r=davidtwco p=1 (conflict prone) |
bors
commented
Mar 8, 2023
📌 Commit 03cc5131e56062d177a32695334fd3a818b6381d has been approved by It is now in the queue for this repository. |
bors
commented
Mar 9, 2023
☔ The latest upstream changes (presumably #108919) made this pull request unmergeable. Please resolve the merge conflicts. |
est31
commented
Mar 9, 2023
Hmm yeah getting this merged is a bit difficult, like #103042 was. outside of splitting it up or p=10 above rollups, the only chance is to wait until the stars line up so that no rollup PR is in the queue (usually those do change ftl files), and a PR is currently being tried that doesn't modify ftl files. Then one would rebase right at that moment, and and approve the pr. I will spend the next week looking for opportunities to merge this. If there is still none, I will just set p=10. |
compiler-errors
commented
Mar 9, 2023
I would wait until the queue is calmed down, then land it with p=10. |
This makes it easier to open the messages file while developing on features. The commit was the result of automatted changes: for p in compiler/rustc_*; do mv $p/locales/en-US.ftl $p/messages.ftl; rmdir $p/locales; done for p in compiler/rustc_*; do sed -i "s#\.\./locales/en-US.ftl#../messages.ftl#" $p/src/lib.rs; done
est31
commented
Mar 11, 2023
Okay, I'd say it's calmed down now, only 26 PRs waiting for admittance now. @bors r=davidtwco |
bors
commented
Mar 11, 2023
bors
commented
Mar 12, 2023
💔 Test failed - checks-actions |
est31
commented
Mar 12, 2023
bors
commented
Mar 12, 2023
bors
commented
Mar 12, 2023
☀️ Test successful - checks-actions |
rust-timer
commented
Mar 12, 2023
Finished benchmarking commit (501ad02): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. |
rust-log-analyzer
commented
Mar 14, 2023
The job Click to see the possible cause of the failure (guessed by this bot) |
This makes it easier to open the messages file. Right now I have to first click on the
localesdir to open it, and then on theen-US.ftlfile.Cargo.tomlandbuild.rsfiles are also in the top level, and I think there should not be more than one file, so a directory isn't really needed. The chosen strategy for pontoon adoption is out of tree. Even if this descision is changed in the future, themessages.ftlapproach is also compatible with non-english translations living in-tree, as long as the non-english translations don't live in thecompiler/rustc_foo/directories but in different ones. That would also be helpful for grepability purposes.The commit was the result of automated changes:
r? @davidtwco