Module: website Branch: master Commit: 4aed87ed5f4d1575b1a04c0e4024c37a4ff95119 URL: http://source.winehq.org/git/website.git/?a=commit;h=4aed87ed5f4d1575b1a04c0...
Author: André Hentschel nerv@dawncrow.de Date: Wed Nov 3 19:45:02 2010 +0100
Replace some cvs stuff
---
templates/de/contributing.template | 5 ++--- templates/en/contributing.template | 2 +- templates/en/status/wine.template | 2 +- templates/he/contributing.template | 2 +- templates/he/status/wine.template | 2 +- templates/pt/contributing.template | 4 ++-- 6 files changed, 8 insertions(+), 9 deletions(-)
diff --git a/templates/de/contributing.template b/templates/de/contributing.template index ff3333d..a1c94eb 100644 --- a/templates/de/contributing.template +++ b/templates/de/contributing.template @@ -265,8 +265,7 @@ <p>Wine hat einen ständigen Bedarf an Aktualisierungen der Dokumentation. Wine hat seine "<a href="{$root}/site/documentation">Anleitungen (en)</a>", wie den Wine User Guide etc. Die SGML-Quellen der Anleitungen befinden sich in einem - <a href="http://www.winehq.org/site/cvs#docs">separatem CVS Zweig auf - Sourceforge</a>.</p> + <a href="http://source.winehq.org/git/docs.git/">separate Git Zweig</a>.</p> <p>Weitere wichtige Dokumentationen sind die README Datei und die man pages und anderen Dateien im documentation Verzeichnis.</p> <p>Deine Aufgabe wäre es sicherzustellen, dass jeder Patch, der von einem @@ -276,7 +275,7 @@ Entwickler fragen, was ihr Patch im Einzelnen macht (und vergiss nicht, den Entwicklern einen zu verpassen, die die Arbeitsweise ihres Patches überhaupt nicht dokumentiert haben!).</p> -<p>Die Aktualisierung der Dokumentation findet statt, in dem Du "CVS Diffs" der +<p>Die Aktualisierung der Dokumentation findet statt, in dem Du "Git Diffs" der entsprechenden Dateien an wine-patches schickst.</p>
<p>Benötigte Fertigkeiten/Kenntnisse:</p> diff --git a/templates/en/contributing.template b/templates/en/contributing.template index d292086..f868af5 100644 --- a/templates/en/contributing.template +++ b/templates/en/contributing.template @@ -245,7 +245,7 @@ functionality and optionally asking developers about what their patch truly does (and of course don't forget to beat up developers that don't document the workings of their patch at all!).</p> -<p>The documentation updates would be done by sending "cvs diff"s of the +<p>The documentation updates would be done by sending "git diff"s of the relevant files to wine-patches.</p> <p>Requirements:</p> <ul> diff --git a/templates/en/status/wine.template b/templates/en/status/wine.template index f2b8a9d..265e606 100644 --- a/templates/en/status/wine.template +++ b/templates/en/status/wine.template @@ -558,7 +558,7 @@ </tr> <tr> <td>Wine DLL dump utility (winedump)</td> - <td class="good"><a href="http://cvs.winehq.org/cvsweb/wine/tools/winedump/README">Good</a></td> + <td class="good"><a href="http://source.winehq.org/git/wine.git/?a=blob;f=tools/winedump/README">Good</a></td> <td><a href="{$root}/wwn/305#Demangling%20Symbols">#305</a></td> <td class="pct90">90% complete</td> <td></td> diff --git a/templates/he/contributing.template b/templates/he/contributing.template index ed009ed..088b5b5 100644 --- a/templates/he/contributing.template +++ b/templates/he/contributing.template @@ -243,7 +243,7 @@ functionality and optionally asking developers about what their patch truly does (and of course don't forget to beat up developers that don't document the workings of their patch at all!).</p> -<p>The documentation updates would be done by sending "cvs diff"s of the +<p>The documentation updates would be done by sending "git diff"s of the relevant files to wine-patches.</p> <p>Requirements:</p> <ul> diff --git a/templates/he/status/wine.template b/templates/he/status/wine.template index f2b8a9d..265e606 100644 --- a/templates/he/status/wine.template +++ b/templates/he/status/wine.template @@ -558,7 +558,7 @@ </tr> <tr> <td>Wine DLL dump utility (winedump)</td> - <td class="good"><a href="http://cvs.winehq.org/cvsweb/wine/tools/winedump/README">Good</a></td> + <td class="good"><a href="http://source.winehq.org/git/wine.git/?a=blob;f=tools/winedump/README">Good</a></td> <td><a href="{$root}/wwn/305#Demangling%20Symbols">#305</a></td> <td class="pct90">90% complete</td> <td></td> diff --git a/templates/pt/contributing.template b/templates/pt/contributing.template index baaf979..e3a1e46 100644 --- a/templates/pt/contributing.template +++ b/templates/pt/contributing.template @@ -255,7 +255,7 @@ <p>O Wine está constantemente a necessitar de actualizações à documentação. O Wine tem os seus "<a href="{$root}/site/documentation">Guias</a>" tais como o Wine User Guide etc. O código fonte SGML pode ser encontrado numa - <a href="http://www.winehq.org/site/cvs#docs">árvore CVS à parte na Sourceforge</a>.</p> + <a href="http://source.winehq.org/git/docs.git/">árvore Git à parte</a>.</p> <p>Outros items de documentação importantes são o ficheiro README, as páginas man e outros ficheiros no directório de documentação.</p> <p>O seu trabalho seria certificar-se de que a cada correcção que um programador @@ -264,7 +264,7 @@ a nova funcionalidade e opcionalmente perguntando ao programador o que é que o seu patch faz realmente (e claro não se esqueça de bater em programadores que não documentam nada do funcionamento dos seus patchs!).</p> -<p>As actualizações à documentação seriam efectuadas enviando "diffs cvs" dos +<p>As actualizações à documentação seriam efectuadas enviando "diffs git" dos ficheiros relevantes para o wine-patches.</p> <p>Requisitos:</p> <ul>