| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-06-18 | Merge commit 'fda0bb9588912a3e0606e880ca9f6e913cf8a5a4' into ↵ | Guillaume Gomez | -4/+4 | |
| subtree-update_cg_gcc_2025-06-18 | ||||
| 2025-05-14 | Merge commit '6ba33f5e1189a5ae58fb96ce3546e76b13d090f5' into ↵ | Guillaume Gomez | -4/+5 | |
| subtree-update_cg_gcc_2025-05-14 | ||||
| 2025-04-25 | Merge commit '4f83a4258deb99f3288a7122c0d5a78200931c61' into ↵ | Antoni Boucher | -0/+2 | |
| subtree-update_cg_gcc_2025-04-25 | ||||
| 2025-01-13 | Fix formatting | Antoni Boucher | -5/+3 | |
| 2025-01-13 | Merge commit '59a81c2ca1edc88ad3ac4b27a8e03977ffb8e73a' into ↵ | Antoni Boucher | -8/+16 | |
| subtree-update_cg_gcc_2025_01_12 | ||||
| 2024-07-10 | Merge commit '98ed962c7d3eebe12c97588e61245273d265e72f' into master | Guillaume Gomez | -2/+1 | |
| 2024-06-20 | Add blank lines after module-level `//!` comments. | Nicholas Nethercote | -0/+1 | |
| Most modules have such a blank line, but some don't. Inserting the blank line makes it clearer that the `//!` comments are describing the entire module, rather than the `use` declaration(s) that immediately follows. | ||||
| 2024-03-05 | Merge commit 'b385428e3ddf330805241e7758e773f933357c4b' into ↵ | Guillaume Gomez | -41/+47 | |
| subtree-update_cg_gcc_2024-03-05 | ||||
| 2023-10-26 | Merge commit 'e4fe941b11a55c5005630696e9b6d81c65f7bd04' into ↵ | Antoni Boucher | -4/+66 | |
| subtree-update_cg_gcc_2023-10-25 | ||||
| 2023-03-05 | Merge commit '08a6d6e16b5efe217123e780398969946266268f' into ↵ | Antoni Boucher | -1/+5 | |
| sync-cg_gcc-2023-03-04 | ||||
| 2022-06-06 | Merge commit 'e8dca3e87d164d2806098c462c6ce41301341f68' into sync_from_cg_gcc | Antoni Boucher | -0/+68 | |
