Remove references to non-existing page anchor

stomar · stomar · commit e45d9a134114 · 2013-02-24T12:27:27.000+01:00
diff --git a/bg/community/ruby-core/index.md b/bg/community/ruby-core/index.md
@@ -46,7 +46,7 @@ Subversion FAQ][1] и [the Subversion book][2]. Друг вариент е кн
 
 Основния екип поддържа [a bug tracker][4] за приемането на кръпки и
 репорти за бъгове. Тези репорти се публикуват също така и в пощенския
-списък [Ruby-Core mailing list](/en/community/mailing-lists/#ruby-core)
+списък [Ruby-Core mailing list](/en/community/mailing-lists/)
 за дискусия.
 
 На кратко стъпките за изготвянето на кръпка:
@@ -63,15 +63,15 @@ Subversion FAQ][1] и [the Subversion book][2]. Друг вариент е кн
      $ svn diff > ruby-changes.patch
     `
 4.  Пратете елетронно писмо до [Ruby-Core mailing
-    list](/en/community/mailing-lists/#ruby-core) с CHANGELOG, описващ
+    list](/en/community/mailing-lists/) с CHANGELOG, описващ
     кръпката.
 5.  Ако няма проблеми с кръпката, тя ще бъде предадена за одобрение.
 
 **Забележка:** кръпките трябва да бъдат изпратени като [unified
 diff][5]. За повече информация вижте [the diffutils reference][6].
 
 Дискусията ще бъде пренесена на пощенския списък [Ruby-Core mailing
-list](/en/community/mailing-lists/#ruby-core).
+list](/en/community/mailing-lists/).
 
 Помнете, че екипа, който разработва Ruby живее в Япония и въпреки, че
 повечето владеят английски, има съществена часова разлика. Бъдете
diff --git a/de/community/ruby-core/index.md b/de/community/ruby-core/index.md
@@ -85,7 +85,7 @@ werden. Wer mehr über das Zusammenführen (Merge) der Patche wissen will,
 sollte sich [die diffutils reference][11] ansehen.
 
 Diskussionen zum Thema Entwicklungszusammenführung finden sich unter
-[Ruby-Core mailing list](/de/community/mailing-lists/#ruby-core). Wer
+[Ruby-Core mailing list](/de/community/mailing-lists/). Wer
 herausfinden will, ob sein Patch sinn macht oder nur eine Diskussion
 über die Zukunft von Ruby anfangen will, sollte nicht zögern an Bord zu
 kommen. Es wird an dieser Stelle davor gewarnt, Off-Topic Diskussionen
diff --git a/en/community/ruby-core/index.md b/en/community/ruby-core/index.md
@@ -71,7 +71,7 @@ and [everybody else][9].
 
 The core team maintains [a bug tracker][10] for submitting patches and
 bug reports to Matz and the gang. These reports also get submitted to
-the [Ruby-Core mailing list](/en/community/mailing-lists/#ruby-core) for
+the [Ruby-Core mailing list](/en/community/mailing-lists/) for
 discussion, so you can be sure your request won’t go unnoticed. You can
 also send your patches straight to the mailing list. Either way, you are
 encouraged to take part in the discussion that ensues.
@@ -99,7 +99,7 @@ To summarize, the steps for building a patch are:
         $ svn diff > ruby-changes.patch
 
 4.  Email your patch to the [Ruby-Core mailing
-    list](/en/community/mailing-lists/#ruby-core) with a CHANGELOG entry
+    list](/en/community/mailing-lists/) with a CHANGELOG entry
     describing the patch.
 
 5.  If there are no issues raised about the patch, committers will be
@@ -109,7 +109,7 @@ To summarize, the steps for building a patch are:
 For more on how patches are merged, see [the diffutils reference][13].
 
 Discussion of Ruby’s development converges on the [Ruby-Core mailing
-list](/en/community/mailing-lists/#ruby-core). So, if you are curious
+list](/en/community/mailing-lists/). So, if you are curious
 about whether your patch is worthwhile or you want to spark a discussion
 about Ruby’s future, don’t hesitate to come aboard. Be warned that
 off-topic discussions are not tolerated on this list, the noise level
diff --git a/fr/community/ruby-core/index.md b/fr/community/ruby-core/index.md
@@ -91,7 +91,7 @@ diff*][11]. Pour plus d’informations sur les patchs, leur devenir, voyez
 
 Les discussions portant sur le développement de Ruby sont toutes
 regroupées sur la [liste de diffusion
-Ruby-Core](/en/community/mailing-lists/#ruby-core). Donc, si vous êtes
+Ruby-Core](/en/community/mailing-lists/). Donc, si vous êtes
 curieux du devenir de votre patch, ou si vous voulez lancer une
 discussion sur le futur de Ruby, n’hésitez pas à venir y faire un tour.
 Prenez garde à ne pas lancer des hors-sujets, ils ne sont pas tolérés
diff --git a/id/community/ruby-core/index.md b/id/community/ruby-core/index.md
@@ -56,7 +56,7 @@ Subversion][5] sebagai buku yang berguna untuk pengenalan svn.
 Rubyforge mempunyai [bug tracker][6] dengan submit patch dan bug report
 (laporan adanya bug) ke Matz dan rekan-rekan lainnya (Developer Ruby
 Core). Laporan-laporan ini juga di submit ke [milis
-Ruby-Core](/id/community/mailing-lists/#ruby-core) untuk didiskusikan,
+Ruby-Core](/id/community/mailing-lists/) untuk didiskusikan,
 jadi Anda bisa mengkonfirmasi terlebih dahulu apakah permintaan Anda
 akan diperhatikan atau tidak. Anda juga bisa mengirim patch langsung ke
 milis. Anda diharapkan untuk berpartisipasi aktif dalam diskusi
@@ -78,7 +78,7 @@ berikut:
      $ svn diff > ruby-changes.patch
     `
 4.  Email patch Anda ke [milis
-    Ruby-Core](/id/community/mailing-lists/#ruby-core) dengan entri
+    Ruby-Core](/id/community/mailing-lists/) dengan entri
     CHANGELOG yang menjelaskan patch.
 5.  Jika tidak ada masalah dengan patch, maka para committer akan
     melakukan patch tersebut.
@@ -88,7 +88,7 @@ Untuk mengetahui lebih lanjut tentang bagaimana patch digabungkan
 (*merge*), lihat [the diffutils reference][8].
 
 Diskusi tentang pengembangan Ruby dibicarakan di [milis
-Ruby-Core](/id/community/mailing-lists/#ruby-core). Jadi kalau Anda
+Ruby-Core](/id/community/mailing-lists/). Jadi kalau Anda
 penasaran apakah patch Anda berguna atau tidak atau bila Anda ingin
 memulai diskusi tentang masa depan Ruby, jangan sungkan untuk datang
 kemari. Jangan mempost hal-hal di luar topik (OOT) karena milis ini
diff --git a/it/community/ruby-core/index.md b/it/community/ruby-core/index.md
@@ -52,7 +52,7 @@ introduttivo è il [Pragmatic Version Control with Subversion][4].
 Rubyforge mantiene un [bug tracker][5] per notificare patch e
 segnalazioni di errori a Matz e al resto del gruppo. Questi rapporti
 vengono anche notificati alla Ruby-Core mailing
-list”:/en/community/mailing-lists/#ruby-core per discussione, e quindi
+list”:/en/community/mailing-lists/ per discussione, e quindi
 puoi essere sicuro che la tua richiesta non sarà ignorata. Puoi anche
 inviare le tue patch alla mailing list. In ogni caso, non esitare a
 prendere parte alla discussione che ne seguirà.
@@ -73,7 +73,7 @@ In sintesi, i passi per costruire un patch sono:
      $ svn diff > ruby-changes.patch
     `
 4.  Invia per email la tua patch alla [Ruby-Core mailing
-    list](/en/community/mailing-lists/#ruby-core)” con una entry sul
+    list](/en/community/mailing-lists/)” con una entry sul
     CHANGELOG che descrive la patch.
 5.  Se non ci sono obiezioni alla patch, i committer daranno
     l’approvazione per applicarla.
@@ -83,7 +83,7 @@ notificate come un [unified diff][6]. Per ulteriori informazioni sulla
 procedura di merge dei patch , vedi [the diffutils reference][7].
 
 La discussione sullo sviluppo di Ruby converge sulla [Ruby-Core mailing
-list](/en/community/mailing-lists/#ruby-core). Quindi, se hai curiosità
+list](/en/community/mailing-lists/). Quindi, se hai curiosità
 di sapere se il tuo patch è utile oppure se vuoi innescare una
 discussione sul futuro di Ruby, non esitare ad entrare nella mischia.
 Tuttavia, tieni presente che: discussioni fuori soggetto non sono
diff --git a/zh_TW/community/ruby-core/index.md b/zh_TW/community/ruby-core/index.md
@@ -65,7 +65,7 @@ and [everybody else][9].
 
 The core team maintains [a bug tracker][10] for submitting patches and
 bug reports to Matz and the gang. These reports also get submitted to
-the [Ruby-Core mailing list](/en/community/mailing-lists/#ruby-core) for
+the [Ruby-Core mailing list](/en/community/mailing-lists/) for
 discussion, so you can be sure your request won’t go unnoticed. You can
 also send your patches straight to the mailing list. Either way, you are
 encouraged to take part in the discussion that ensues.
@@ -88,7 +88,7 @@ To summarize, the steps for building a patch are:
      $ svn diff > ruby-changes.patch
     `
 4.  Email your patch to the [Ruby-Core mailing
-    list](/en/community/mailing-lists/#ruby-core) with a CHANGELOG entry
+    list](/en/community/mailing-lists/) with a CHANGELOG entry
     describing the patch.
 5.  If there are no issues raised about the patch, committers will be
     given the approval to apply it.
@@ -97,7 +97,7 @@ To summarize, the steps for building a patch are:
 For more on how patches are merged, see [the diffutils reference][13].
 
 Discussion of Ruby’s development converges on the [Ruby-Core mailing
-list](/en/community/mailing-lists/#ruby-core). So, if you are curious
+list](/en/community/mailing-lists/). So, if you are curious
 about whether your patch is worthwhile or you want to spark a discussion
 about Ruby’s future, don’t hesitate to come aboard. Be warned that
 off-topic discussions are not tolerated on this list, the noise level
diff --git a/zh_cn/community/ruby-core/index.md b/zh_cn/community/ruby-core/index.md
@@ -49,7 +49,7 @@ Control with Subversion][4] to be a useful introductory book.
 
 The core team maintains [a bug tracker][5] for submitting patches and
 bug reports to Matz and the gang. These reports also get submitted to
-the [Ruby-Core mailing list](/en/community/mailing-lists/#ruby-core) for
+the [Ruby-Core mailing list](/en/community/mailing-lists/) for
 discussion, so you can be sure your request won’t go unnoticed. You can
 also send your patches straight to the mailing list. Either way, you are
 encouraged to take part in the discussion that ensues.
@@ -69,7 +69,7 @@ To summarize, the steps for building a patch are:
      $ svn diff > ruby-changes.patch
     `
 4.  Email your patch to the [Ruby-Core mailing
-    list](/en/community/mailing-lists/#ruby-core) with a CHANGELOG entry
+    list](/en/community/mailing-lists/) with a CHANGELOG entry
     describing the patch.
 5.  If there are no issues raised about the patch, committers will be
     given the approval to apply it.
@@ -78,7 +78,7 @@ To summarize, the steps for building a patch are:
 more on how patches are merged, see [the diffutils reference][7].
 
 Discussion of Ruby’s development converges on the [Ruby-Core mailing
-list](/en/community/mailing-lists/#ruby-core). So, if you are curious
+list](/en/community/mailing-lists/). So, if you are curious
 about whether your patch is worthwhile or you want to spark a discussion
 about Ruby’s future, don’t hesitate to come aboard. Be warned that
 off-topic discussions are not tolerated on this list, the noise level
