Skip to content

Commit f310fec

Browse files
authored
Merge pull request #616 from nikomatsakis/fix-ice-breaker-links
fix ice-breaker URLs
2 parents bb4328e + 0170af2 commit f310fec

File tree

2 files changed

+15
-7
lines changed

2 files changed

+15
-7
lines changed

posts/inside-rust/2019-10-22-LLVM-ICE-breakers.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,11 @@ Today I'm announcing a new experiment in the compiler team, the **LLVM ICE-break
1212

1313
At its heart, the LLVM ICE-breaker group is just a list of people who would like to be notified when we come across LLVM bugs. You can add yourself to this list very easily -- just [open a PR]! When we come across a suitable bug, we'll write a message that `@`-mentions every Github user on that list. If you have some time, maybe you can fix one of them, or at least offer some words of wisdom to help somebody else figure out what's going on.
1414

15-
[open a PR]: https://rustc-dev-guide.rust-lang.org/ice-breaker/about.html#join
15+
[open a PR]: https://rustc-dev-guide.rust-lang.org/notification-groups/about.html#join
1616

1717
There are a few other things associated with the group too, however. For example, we've got a [guide][llvm guide] that offers some tips for how to fix LLVM-related bugs and may help you get started (particularly if you're not that familiar with rustc).
1818

19-
[llvm guide]: https://rustc-dev-guide.rust-lang.org/ice-breaker/llvm.html
19+
[llvm guide]: https://rustc-dev-guide.rust-lang.org/notification-groups/llvm.html
2020

2121
### What kind of bugs are we talking about?
2222

@@ -25,7 +25,7 @@ The goal is to identify "self-contained" bugs that are unlikely to require large
2525
As Rust developers triage bugs and tag them for the ICE-breakers,
2626
they will [ping][tag syntax] the group on Github.
2727

28-
[tag syntax]: https://rustc-dev-guide.rust-lang.org/ice-breaker/about.html#tagging-an-issue-for-an-ice-breaker-group
28+
[tag syntax]: https://rustc-dev-guide.rust-lang.org/notification-groups/about.html#tagging-an-issue-for-a-notification-group
2929

3030
### Who should join?
3131

@@ -53,8 +53,12 @@ I certainly hope so! As I mentioned before, this is an experiment, but presuming
5353
The current list of ICE-breaker groups is documented in the
5454
[rustc development guide][rustc dev guide]
5555

56-
[rustc dev guide]: https://rustc-dev-guide.rust-lang.org/ice-breaker/about.html
56+
[rustc dev guide]: https://rustc-dev-guide.rust-lang.org/notification-groups/about.html
5757

5858
### So how do I sign up again?
5959

6060
Easy! Just [open a PR]!
61+
62+
### Update
63+
64+
Since this blog post was written, the "ICE-breaker" groups have been renamed to "notification groups".

posts/inside-rust/2020-02-06-Cleanup-Crew-ICE-breakers.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,13 @@ bug, we'll [write a message][tag syntax] that `@`-mentions every Github user on
3737
team. If you have some time, maybe you can provide some useful
3838
information.
3939

40-
[instructions here]: https://rustc-dev-guide.rust-lang.org/ice-breaker/about.html#join
40+
[instructions here]: https://rustc-dev-guide.rust-lang.org/notification-groups/about.html#join
4141

42-
[tag syntax]: https://rustc-dev-guide.rust-lang.org/ice-breaker/about.html#tagging-an-issue-for-an-ice-breaker-group
42+
[tag syntax]: https://rustc-dev-guide.rust-lang.org/notifiation-groups/about.html#tagging-an-issue-for-a-notification-group
4343

4444
You can find more information about the group on it's [rustc-dev-guide
45-
section](https://rustc-dev-guide.rust-lang.org/ice-breaker/cleanup-crew.html).
45+
section](https://rustc-dev-guide.rust-lang.org/notification-groups/cleanup-crew.html).
46+
47+
### Update
48+
49+
Since this blog post was written, the "ICE-breaker" groups have been renamed to "notification groups".

0 commit comments

Comments
 (0)