Permalink
Browse files

Updated links to new repository.

  • Loading branch information...
Brian Ford
Brian Ford committed Jun 7, 2011
1 parent 88c38fc commit 24758b41853ca490e2abe4e94bd63cd537e2b36d
Showing with 51 additions and 51 deletions.
  1. +1 −1 web/doc/de/contributing.markdown
  2. +1 −1 web/doc/de/getting-started/building.markdown
  3. +1 −1 web/doc/de/getting-started/troubleshooting.markdown
  4. +1 −1 web/doc/de/how-to/fix-a-failing-spec.markdown
  5. +1 −1 web/doc/de/how-to/write-a-ruby-spec.markdown
  6. +1 −1 web/doc/de/how-to/write-a-ticket.markdown
  7. +1 −1 web/doc/de/what-is-rubinius.markdown
  8. +1 −1 web/doc/en/garbage-collector/large-objects.markdown
  9. +1 −1 web/doc/en/garbage-collector/mature-generation.markdown
  10. +1 −1 web/doc/en/getting-started/building.markdown
  11. +1 −1 web/doc/en/how-to/fix-a-failing-spec.markdown
  12. +1 −1 web/doc/en/how-to/write-a-blog-post.markdown
  13. +1 −1 web/doc/en/how-to/write-a-ruby-spec.markdown
  14. +1 −1 web/doc/en/how-to/write-a-ticket.markdown
  15. +1 −1 web/doc/en/systems/concurrency.markdown
  16. +1 −1 web/doc/en/tools/memory-analysis.markdown
  17. +1 −1 web/doc/en/what-is-rubinius.markdown
  18. +1 −1 web/doc/es/getting-started/building.markdown
  19. +1 −1 web/doc/es/how-to/fix-a-failing-spec.markdown
  20. +1 −1 web/doc/es/how-to/write-a-ruby-spec.markdown
  21. +1 −1 web/doc/es/how-to/write-a-ticket.markdown
  22. +1 −1 web/doc/es/what-is-rubinius.markdown
  23. +1 −1 web/doc/fr/getting-started/building.markdown
  24. +1 −1 web/doc/fr/how-to/fix-a-failing-spec.markdown
  25. +1 −1 web/doc/fr/how-to/write-a-blog-post.markdown
  26. +1 −1 web/doc/fr/how-to/write-a-ruby-spec.markdown
  27. +1 −1 web/doc/fr/how-to/write-a-ticket.markdown
  28. +1 −1 web/doc/fr/systems/concurrency.markdown
  29. +1 −1 web/doc/fr/tools/memory-analysis.markdown
  30. +1 −1 web/doc/fr/what-is-rubinius.markdown
  31. +1 −1 web/doc/ja/getting-started/building.markdown
  32. +1 −1 web/doc/ja/how-to/fix-a-failing-spec.markdown
  33. +1 −1 web/doc/ja/how-to/write-a-ruby-spec.markdown
  34. +1 −1 web/doc/ja/how-to/write-a-ticket.markdown
  35. +1 −1 web/doc/ja/what-is-rubinius.markdown
  36. +1 −1 web/doc/pl/getting-started/building.markdown
  37. +1 −1 web/doc/pl/how-to/fix-a-failing-spec.markdown
  38. +1 −1 web/doc/pl/how-to/write-a-ruby-spec.markdown
  39. +1 −1 web/doc/pl/how-to/write-a-ticket.markdown
  40. +1 −1 web/doc/pl/what-is-rubinius.markdown
  41. +1 −1 web/doc/pt-br/getting-started/building.markdown
  42. +1 −1 web/doc/pt-br/how-to/fix-a-failing-spec.markdown
  43. +1 −1 web/doc/pt-br/how-to/write-a-blog-post.markdown
  44. +1 −1 web/doc/pt-br/how-to/write-a-ruby-spec.markdown
  45. +1 −1 web/doc/pt-br/how-to/write-a-ticket.markdown
  46. +1 −1 web/doc/pt-br/what-is-rubinius.markdown
  47. +1 −1 web/doc/ru/getting-started/building.markdown
  48. +1 −1 web/doc/ru/how-to/fix-a-failing-spec.markdown
  49. +1 −1 web/doc/ru/how-to/write-a-ruby-spec.markdown
  50. +1 −1 web/doc/ru/how-to/write-a-ticket.markdown
  51. +1 −1 web/doc/ru/what-is-rubinius.markdown
@@ -73,4 +73,4 @@ andere ebenso davon profitieren und verstehen, wie Rubinius implementiert ist.
* Alte Tickets prüfen oder schließen
* Minitests schreiben, die die Fehler reproduzieren. Anschließend prüfen,
ob es schon Specs für diese Fälle gibt. Wenn nicht, evtl. welche schreiben.
-
+
@@ -34,7 +34,7 @@ werden](http://rubini.us/download/latest).
Um Git zu nutzen:
1. Wechsle in dein Entwicklungsverzeichnis
- 2. `git clone git://github.com/evanphx/rubinius.git`
+ 2. `git clone git://github.com/rubinius/rubinius.git`
### Rubinius installieren
@@ -50,4 +50,4 @@ Lösung:
Generell sollte das Quell- oder Kompilierverzeichnis nicht nach dem Kompilieren
umbenannt werden.
-
+
@@ -38,7 +38,7 @@ beheben:
willst.
11. Erstelle ein Gist (auf http://gist.github.com) mit deinem Patch und
verlinke es in einem neuen Ticket im Issuetracker auf Github:
- http://github.com/evanphx/rubinius/issues Es können mehrere Patches pro
+ http://github.com/rubinius/rubinius/issues Es können mehrere Patches pro
Ticket hinzugefügt werden.
Wenn dein Patch vom Rubinius Projekt akzeptiert wird, erhältst du ein sog.
@@ -23,4 +23,4 @@ schreiben:
7. Führe `git format-patch` aus
8. Erstelle ein Gist (auf http://gist.github.com) mit deinem Patch und
verlinke diesen in einem Ticket auf dem Issuetracker:
- <http://github.com/evanphx/rubinius/issues>
+ <http://github.com/rubinius/rubinius/issues>
@@ -8,7 +8,7 @@ next_url: how-to/write-a-ruby-spec
---
Den Rubinius Issuetracker findest du hier:
-<http://github.com/evanphx/rubinius/issues>.
+<http://github.com/rubinius/rubinius/issues>.
Damit ein Ticket nützlich ist, sollte es prägnant, fokussiert und umsetzbar
sein. Falls es diese Kriterien nicht erfüllt, wird es vermutlich nur den
@@ -29,7 +29,7 @@ Windows Unterstützung kommt ebenfalls bald und ist derzeit in Entwicklung.
Um Rubinius zu installieren, folge den unteren Anweisungen. Für detailliertere
Informationen siehe auch: [Erste Schritte](/doc/de/getting-started/).
-1. `git clone git://github.com/evanphx/rubinius.git`
+1. `git clone git://github.com/rubinius/rubinius.git`
1. `cd rubinius`
1. `./configure --prefix=/pfad/zum/installations/verzeichnis`
1. `rake install`
@@ -19,5 +19,5 @@ object* which by default is 2700 (such a good baud rate eh?) bytes.
rbx ... -Xgc.large_object=<number of bytes> ...
For more information on configuration variables available read the
-[vm configuration source file ](https://github.com/evanphx/rubinius/blob/master/vm/configuration.hpp)
+[vm configuration source file ](https://github.com/rubinius/rubinius/blob/master/vm/configuration.hpp)
@@ -15,5 +15,5 @@ mature collection occurrs. This can be turned off or a static number may be used
via gc.lifetime. gc.lifetime is used by autotune which sets the initial value.
For more information on configuration variables available read the
-[vm configuration source file ](https://github.com/evanphx/rubinius/blob/master/vm/configuration.hpp)
+[vm configuration source file ](https://github.com/rubinius/rubinius/blob/master/vm/configuration.hpp)
@@ -26,7 +26,7 @@ You can [download the tarball here](http://rubini.us/download/latest).
To use Git:
1. Change your current working directory to your development directory
- 2. `git clone git://github.com/evanphx/rubinius.git`
+ 2. `git clone git://github.com/rubinius/rubinius.git`
### Installing Rubinius
@@ -31,7 +31,7 @@ Then, follow these steps to fix a failing spec:
-N', where N is the number (1, 2, etc.) of commits for which you want to
generate patches.
11. Create a gist with your patch and link to it in a ticket on the issue
- tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
+ tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
patches to one ticket.
When your patch is accepted by the Rubinius project, you'll get a commit bit
@@ -16,7 +16,7 @@ formatting needs, the post can be written in HTML directly.
Clone Rubinius repository as that is where the website and posts are stored.
- git clone https://github.com/evanphx/rubinius.git
+ git clone https://github.com/rubinius/rubinius.git
To get started, ensure you have the `kramdown` and `jekyll` gems installed.
@@ -20,4 +20,4 @@ Then, follow these steps to write a spec for a Ruby method:
4. Commit your changes
7. Use `git format-patch`
8. Create a gist with your patch and link to it in a ticket on the issue
- tracker at <http://github.com/evanphx/rubinius/issues>.
+ tracker at <http://github.com/rubinius/rubinius/issues>.
@@ -7,7 +7,7 @@ next: Write a Ruby Spec
next_url: how-to/write-a-ruby-spec
---
-The Rubinius issue tracker is <http://github.com/evanphx/rubinius/issues>.
+The Rubinius issue tracker is <http://github.com/rubinius/rubinius/issues>.
To be useful, tickets must be concise, focused, and actionable. If not, the
ticket will languish and become clutter. Accordingly, tickets must fall into
@@ -91,4 +91,4 @@ Actors can also have a parent/child relationship using `Actor.spawn_link`; if th
end
sleep 1
-This example is a snippet from [girl_friday](http://github.com/mperham/girl_friday). You can review that codebase for more detail if you have questions.
+This example is a snippet from [girl_friday](http://github.com/mperham/girl_friday). You can review that codebase for more detail if you have questions.
@@ -239,4 +239,4 @@ problem.
As it turns out, the `ZMQ::Message` class allocates some memory via `malloc` that is not
tracked by the Rubinius GC. It needs to be manually deallocated.
-Changing the code to call `ZMQ::Message#close` resolves the last leak.
+Changing the code to call `ZMQ::Message#close` resolves the last leak.
@@ -29,7 +29,7 @@ Microsoft Windows is coming soon.
To install Rubinius, use the following steps. For more detailed information,
see [Getting Started](/doc/en/getting-started/).
-1. `git clone git://github.com/evanphx/rubinius.git`
+1. `git clone git://github.com/rubinius/rubinius.git`
1. `cd rubinius`
1. `./configure --prefix=/path/to/install/dir`
1. `rake install`
@@ -28,7 +28,7 @@ Para usar Git:
1. Utilice la linea de comandos para entrar a su directorio de
desarrollo.
- 2. `git clone git://github.com/evanphx/rubinius.git`
+ 2. `git clone git://github.com/rubinius/rubinius.git`
### Instalación de Rubinius
@@ -32,7 +32,7 @@ Then, follow these steps to fix a failing spec:
-N', where N is the number (1, 2, etc.) of commits for which you want to
generate patches.
11. Create a gist with your patch and link to it in a ticket on the issue
- tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
+ tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
patches to one ticket.
When your patch is accepted by the Rubinius project, you'll get a commit bit
@@ -21,4 +21,4 @@ Then, follow these steps to write a spec for a Ruby method:
4. Commit your changes
7. Use `git format-patch`
8. Create a gist with your patch and link to it in a ticket on the issue
- tracker at http://github.com/evanphx/rubinius/issues.
+ tracker at http://github.com/rubinius/rubinius/issues.
@@ -8,7 +8,7 @@ next_url: how-to/write-a-ruby-spec
translated: true
---
-The Rubinius issue tracker is <http://github.com/evanphx/rubinius/issues>.
+The Rubinius issue tracker is <http://github.com/rubinius/rubinius/issues>.
Para ser útiles, los boletos deben ser concisas, específicas y acciones
concretas. Si no, el boleto languidecen y se convierten en el desorden. En
@@ -29,7 +29,7 @@ pronto estará disponible tambien en plataformas Microsoft Windows.
Para instalar Rubinius, realize los siguientes pasos. Para obtener información
más detallada, vea [Primeros pasos](/doc/es/getting-started/).
-1. `git clone git://github.com/evanphx/rubinius.git`
+1. `git clone git://github.com/rubinius/rubinius.git`
1. `cd rubinius`
1. `./configure --prefix=/path/to/install/dir`
1. `rake install`
@@ -29,7 +29,7 @@ Vous pouvez [télécharger l'archive ici](http://rubini.us/download/latest).
Pour utiliser Git :
1. Changez de répertoire courant vers votre répertoire de développement
- 2. `git clone git://github.com/evanphx/rubinius.git`
+ 2. `git clone git://github.com/rubinius/rubinius.git`
### Installer Rubinius
@@ -25,7 +25,7 @@ Ensuite, suivez ces étapes pour corriger un test en échec:
9. Exécutez `git status, git add, git commit`, etc. Tout changement apporté aux fichiers de tests sous le dossier
spec/ruby doit être dans un commit différent de celui utilisé pour corriger le code source.
10. Exécutez `git format-patch origin`, ce qui extraira les commits accumulés dans la branche en cours depuis sa dernière mise à jour depuis origin, ou `git format-patch -N', ou N (un entier, 1, 2,...) est le nombre de commits que vous souhaitez extraire afin de génerer le patch
- 11. Créez un gist avec votre patch et liez-le dans un ticket sur le gestionnaire de ticket du projet http://github.com/evanphx/rubinius/issues. Vous pouvez ajoutez plusieurs patchs à un seul ticket.
+ 11. Créez un gist avec votre patch et liez-le dans un ticket sur le gestionnaire de ticket du projet http://github.com/rubinius/rubinius/issues. Vous pouvez ajoutez plusieurs patchs à un seul ticket.
Quand votre patch est accepté par le project Rubinius, vous aurez un
droit d'accès au dépôt Rubinius. Communiquez votre nom d'utilisateur
@@ -18,7 +18,7 @@ HTML directement.
Clonez le dépôt Rubinius afin de récupérer le site web et les billets.
- git clone https://github.com/evanphx/rubinius.git
+ git clone https://github.com/rubinius/rubinius.git
Pour démarrer, assurez-vous d'avoir installé les gems `kramdown` et `jekyll`.
@@ -20,4 +20,4 @@ Ensuite, suivez ces étapes pour écrire le test d'une méthode Ruby:
historique MRI (aussi connue sous le nom de MatzRuby)
4. Committez vos changements
7. Utilisez `git format-patch`
- 8. Créez un gist avec votre patch et faites référence à ce ticket sur notre gestionnaire de ticket <http://github.com/evanphx/rubinius/issues>.
+ 8. Créez un gist avec votre patch et faites référence à ce ticket sur notre gestionnaire de ticket <http://github.com/rubinius/rubinius/issues>.
@@ -7,7 +7,7 @@ next: Ecrire un Test Ruby
next_url: how-to/write-a-ruby-spec
---
-Le gestionnaire de ticket Rubinius se trouve à l'adresse <http://github.com/evanphx/rubinius/issues>.
+Le gestionnaire de ticket Rubinius se trouve à l'adresse <http://github.com/rubinius/rubinius/issues>.
Pour être utile, un ticket doit être concis, précis et permettre d'agir.
S'il ne l'est pas, le ticket va engendrer des aller-tours, des
@@ -91,4 +91,4 @@ Actors can also have a parent/child relationship using `Actor.spawn_link`; if th
end
sleep 1
-This example is a snippet from [girl_friday](http://github.com/mperham/girl_friday). You can review that codebase for more detail if you have questions.
+This example is a snippet from [girl_friday](http://github.com/mperham/girl_friday). You can review that codebase for more detail if you have questions.
@@ -239,4 +239,4 @@ problem.
As it turns out, the `ZMQ::Message` class allocates some memory via `malloc` that is not
tracked by the Rubinius GC. It needs to be manually deallocated.
-Changing the code to call `ZMQ::Message#close` resolves the last leak.
+Changing the code to call `ZMQ::Message#close` resolves the last leak.
@@ -28,7 +28,7 @@ Le support de Microsoft Windows est à venir prochainement.
Pour installer Rubinius, suivez les instructions suivantes. Pour des informations plus détaillées,
lisez le chapitre [Démarrage](/doc/fr/getting-started/).
-1. `git clone git://github.com/evanphx/rubinius.git`
+1. `git clone git://github.com/rubinius/rubinius.git`
1. `cd rubinius`
1. `./configure --prefix=/path/to/install/dir`
1. `rake install`
@@ -27,7 +27,7 @@ RubiniusのソースコードはtarballとしてのGitHubにプロジェクト
To use Git:
1. Change your current working directory to your development directory
- 2. `git clone git://github.com/evanphx/rubinius.git`
+ 2. `git clone git://github.com/rubinius/rubinius.git`
### Installing Rubinius
@@ -32,7 +32,7 @@ Then, follow these steps to fix a failing spec:
-N', where N is the number (1, 2, etc.) of commits for which you want to
generate patches.
11. Create a gist with your patch and link to it in a ticket on the issue
- tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
+ tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
patches to one ticket.
When your patch is accepted by the Rubinius project, you'll get a commit bit
@@ -21,4 +21,4 @@ Then, follow these steps to write a spec for a Ruby method:
4. Commit your changes
7. Use `git format-patch`
8. Create a gist with your patch and link to it in a ticket on the issue
- tracker at <http://github.com/evanphx/rubinius/issues>.
+ tracker at <http://github.com/rubinius/rubinius/issues>.
@@ -8,7 +8,7 @@ next_url: how-to/write-a-ruby-spec
translated: true
---
-The Rubinius issue tracker is <http://github.com/evanphx/rubinius/issues>.
+The Rubinius issue tracker is <http://github.com/rubinius/rubinius/issues>.
To be useful, tickets must be concise, focused, and actionable. If not, the
ticket will languish and become clutter. Accordingly, tickets must fall into
@@ -30,7 +30,7 @@ Windowsは、すぐに来ている。
Rubiniusのをインストールするには、次の手順を実行します。詳細については、
[はじめに](/doc/ja/getting-started/)を参照してください。
-1. `git clone git://github.com/evanphx/rubinius.git`
+1. `git clone git://github.com/rubinius/rubinius.git`
1. `cd rubinius`
1. `./configure --prefix=/path/to/install/dir`
1. `rake install`
@@ -31,7 +31,7 @@ projekt na Github'ie. Archiwum tar możesz [pobrać tutaj](http://rubini.us/down
Pobieranie źródeł przy pomocy Git'a:
1. `cd docelowy_katalog`
- 2. `git clone git://github.com/evanphx/rubinius.git`
+ 2. `git clone git://github.com/rubinius/rubinius.git`
### Instalacja Rubiniusa
@@ -31,7 +31,7 @@ Then, follow these steps to fix a failing spec:
-N', where N is the number (1, 2, etc.) of commits for which you want to
generate patches.
11. Create a gist with your patch and link to it in a ticket on the issue
- tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
+ tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
patches to one ticket.
When your patch is accepted by the Rubinius project, you'll get a commit bit
@@ -20,4 +20,4 @@ Then, follow these steps to write a spec for a Ruby method:
4. Commit your changes
7. Use `git format-patch`
8. Create a gist with your patch and link to it in a ticket on the issue
- tracker at <http://github.com/evanphx/rubinius/issues>.
+ tracker at <http://github.com/rubinius/rubinius/issues>.
@@ -7,7 +7,7 @@ next: Write a Ruby Spec
next_url: how-to/write-a-ruby-spec
---
-The Rubinius issue tracker is <http://github.com/evanphx/rubinius/issues>.
+The Rubinius issue tracker is <http://github.com/rubinius/rubinius/issues>.
To be useful, tickets must be concise, focused, and actionable. If not, the
ticket will languish and become clutter. Accordingly, tickets must fall into
@@ -30,7 +30,7 @@ Unix/Linux. Wsparcie dla systemu Microsoft Windows jest planowane wkrótce.
Aby zainstalować Rubiniusa wykonaj poniższe kroki. Aby dowiedzieć się
więcej przeczytaj [Pierwsze kroki](/doc/pl/getting-started/).
-1. `git clone git://github.com/evanphx/rubinius.git`
+1. `git clone git://github.com/rubinius/rubinius.git`
1. `cd rubinius`
1. `./configure --prefix=/path/to/install/dir`
1. `rake install`
@@ -26,7 +26,7 @@ You can [download the tarball here](http://rubini.us/download/latest).
To use Git:
1. Change your current working directory to your development directory
- 2. `git clone git://github.com/evanphx/rubinius.git`
+ 2. `git clone git://github.com/rubinius/rubinius.git`
### Installing Rubinius
@@ -31,7 +31,7 @@ Then, follow these steps to fix a failing spec:
-N', where N is the number (1, 2, etc.) of commits for which you want to
generate patches.
11. Create a gist with your patch and link to it in a ticket on the issue
- tracker at http://github.com/evanphx/rubinius/issues. You can add multiple
+ tracker at http://github.com/rubinius/rubinius/issues. You can add multiple
patches to one ticket.
When your patch is accepted by the Rubinius project, you'll get a commit bit
@@ -16,7 +16,7 @@ formatting needs, the post can be written in HTML directly.
Clone Rubinius repository as that is where the website and posts are stored.
- git clone https://github.com/evanphx/rubinius.git
+ git clone https://github.com/rubinius/rubinius.git
To get started, ensure you have the `kramdown` and `jekyll` gems installed.
@@ -20,4 +20,4 @@ Then, follow these steps to write a spec for a Ruby method:
4. Commit your changes
7. Use `git format-patch`
8. Create a gist with your patch and link to it in a ticket on the issue
- tracker at <http://github.com/evanphx/rubinius/issues>.
+ tracker at <http://github.com/rubinius/rubinius/issues>.
@@ -7,7 +7,7 @@ next: Write a Ruby Spec
next_url: how-to/write-a-ruby-spec
---
-The Rubinius issue tracker is <http://github.com/evanphx/rubinius/issues>.
+The Rubinius issue tracker is <http://github.com/rubinius/rubinius/issues>.
To be useful, tickets must be concise, focused, and actionable. If not, the
ticket will languish and become clutter. Accordingly, tickets must fall into
@@ -28,7 +28,7 @@ Para instalar Rubinius, siga os passos abaixo. Para informação mais detalhada
veja [Começando](/doc/pt-br/getting-started/).
-1. `git clone git://github.com/evanphx/rubinius.git`
+1. `git clone git://github.com/rubinius/rubinius.git`
1. `cd rubinius`
1. `./configure --prefix=/path/to/install/dir`
1. `rake install`
@@ -28,7 +28,7 @@ Tar-архив можно скачать [здесь](http://rubini.us/download/
Чтобы использовать Git:
1. Перейдите в директорию для разработок;
- 2. `git clone git://github.com/evanphx/rubinius.git`
+ 2. `git clone git://github.com/rubinius/rubinius.git`
### Установка Rubinius
@@ -33,7 +33,7 @@ next_url: how-to/write-a-blog-post
-N', где N -- число (1, 2, и т.п.) коммитов, из которых вы хотите сделать
патчи.
11. Создайте gist с вашим патчем и добавьте ссылку на него в тикет в трекере
- http://github.com/evanphx/rubinius/issues. В один тикет можно помещать
+ http://github.com/rubinius/rubinius/issues. В один тикет можно помещать
несколько патчей.
Когда ваш патч принят в Rubinius вы можете стать коммитером проекта. Свяжитесь
Oops, something went wrong.

0 comments on commit 24758b4

Please sign in to comment.