[SE-0028] Gmane to Pipermail

Author: kkdevenda

proposals/0028-modernizing-debug-identifiers.md

@@ -2,7 +2,7 @@
 
 * Proposal: [SE-0028](https://github.com/apple/swift-evolution/blob/master/proposals/0028-modernizing-debug-identifiers.md)
 * Author: [Erica Sadun](http://github.com/erica)
-* Status: **Implemented in Swift 2.2** ([Rationale](http://thread.gmane.org/gmane.comp.lang.swift.evolution/5805), Bug: [SR-669](https://bugs.swift.org/browse/SR-669))
+* Status: **Implemented in Swift 2.2** ([Rationale](https://lists.swift.org/pipermail/swift-evolution-announce/2016-February/000030.html), Bug: [SR-669](https://bugs.swift.org/browse/SR-669))
 * Review manager: [Chris Lattner](https://github.com/lattner)
 
 ## Introduction
@@ -67,4 +67,4 @@ The review of SE-0028 "Modernizing Swift's Debugging Identifiers" ran from Janua
 
 * The core team isn’t thrilled with the magic “first token on a line” whitespace behavior that `#line` will be getting, and would like to start a discussion about renaming the old `#line` directive to something more specific and tailored to its purpose.   Once that name and syntax is settled, we can rename the directive and remove the whitespace rule.
 
-* The core team requests that `#symbol` be split out into a separate proposal, because it needs more detailed design work, and is an additive feature.  For example, it might be appealing to provide a `#mangledname` expression that provides the current symbol as a mangled name: when fed into a demangler, a more structured form of the current symbol would be available.
+* The core team requests that `#symbol` be split out into a separate proposal, because it needs more detailed design work, and is an additive feature.  For example, it might be appealing to provide a `#mangledname` expression that provides the current symbol as a mangled name: when fed into a demangler, a more structured form of the current symbol would be available.