diff options
author | Sébastien Helleu <flashcode@flashtux.org> | 2021-02-20 11:12:14 +0100 |
---|---|---|
committer | Sébastien Helleu <flashcode@flashtux.org> | 2021-02-20 11:12:14 +0100 |
commit | 5725c8561ccdd55f0ce466b1ec208047f9c98519 (patch) | |
tree | 764a8592944e52197f53527cca91d62eab43b9a9 /doc | |
parent | 49ac7dd9f59df233e0e8294178b5fd094c28def0 (diff) | |
download | weechat-5725c8561ccdd55f0ce466b1ec208047f9c98519.zip |
doc: remove references to Savannah in developer's guide
Diffstat (limited to 'doc')
-rw-r--r-- | doc/en/weechat_dev.en.adoc | 21 | ||||
-rw-r--r-- | doc/fr/weechat_dev.fr.adoc | 22 | ||||
-rw-r--r-- | doc/ja/weechat_dev.ja.adoc | 22 |
3 files changed, 21 insertions, 44 deletions
diff --git a/doc/en/weechat_dev.en.adoc b/doc/en/weechat_dev.en.adoc index e48cd9a2f..7a30165a5 100644 --- a/doc/en/weechat_dev.en.adoc +++ b/doc/en/weechat_dev.en.adoc @@ -1090,18 +1090,12 @@ Any patch for bug or new feature must be done on master branch, preferred way is a GitHub pull request. A patch can also be sent by e-mail (made with `git diff` or `git format-patch`). -Format of commit message is the following (to close a GitHub issue): +Format of commit message is the following (with automatic close of a GitHub issue): ---- component: fix a problem (closes #123) ---- -For a Savannah bug: - ----- -component: fix a problem (bug #12345) ----- - Where _component_ is one of following: * WeeChat core: _core_ (files in root directory, _po/_ and _src/_, @@ -1114,20 +1108,17 @@ Some rules to follow: * Use only English. * Use infinitive form of verb. -* If commit is related to something in tracker, write it in parenthesis after - the message, with this format: -** GitHub: closes #123 -** Savannah: bug #12345, task #12345, patch #12345 +* If commit is related to a GitHub issue, write it in parenthesis after + the message, with this format: `(issue #123)` or `(closes #123)` to close it. Examples of commit messages: ---- -irc: add command /unquiet (closes #36) core: add callback "nickcmp" for nick comparison in buffers -irc: fix freeze when reading on socket with SSL enabled (bug #35097) -ruby: add detection of ruby version 1.9.3 in CMake +core: update Japanese translations +irc: add command /unquiet (closes #36) python: fix crash when unloading a script without pointer to interpreter -core: update Japanese translations (patch #7783) +ruby: add detection of ruby version 1.9.3 in CMake ---- [[translations]] diff --git a/doc/fr/weechat_dev.fr.adoc b/doc/fr/weechat_dev.fr.adoc index 4e1d98eb3..d4d8fa113 100644 --- a/doc/fr/weechat_dev.fr.adoc +++ b/doc/fr/weechat_dev.fr.adoc @@ -1108,18 +1108,13 @@ Tout patch pour un bug ou une nouvelle fonctionnalité doit être effectué sur branche master, le format préféré étant une "pull request" sur GitHub. Un patch peut aussi être envoyé par e-mail (fait avec `git diff` ou `git format-patch`). -Le format du message de commit est le suivant (pour fermer un bug GitHub) : +Le format du message de commit est le suivant (avec fermeture automatique +du bug GitHub) : ---- component: fix a problem (closes #123) ---- -Pour un bug Savannah : - ----- -component: fix a problem (bug #12345) ----- - Où _component_ est : * pour le cœur WeeChat : _core_ (les fichiers dans le répertoire racine, _po/_ @@ -1132,20 +1127,17 @@ Quelques règles à suivre : * Utilisez seulement l'anglais. * Utilisez des verbes à l'infinitif. -* Si le commit est relatif au tracker, écrivez-le entre parenthèses après le - message, avec ce format : -** GitHub : closes #123 -** Savannah : bug #12345, task #12345, patch #12345 +* Si le commit est relatif à un bug GitHub, écrivez-le entre parenthèses après + le message, avec ce format : `(issue #123)` ou `(closes #123)` pour le fermer. Exemples de messages de commit : ---- -irc: add command /unquiet (closes #36) core: add callback "nickcmp" for nick comparison in buffers -irc: fix freeze when reading on socket with SSL enabled (bug #35097) -ruby: add detection of ruby version 1.9.3 in CMake +core: update Japanese translations +irc: add command /unquiet (closes #36) python: fix crash when unloading a script without pointer to interpreter -core: update Japanese translations (patch #7783) +ruby: add detection of ruby version 1.9.3 in CMake ---- [[translations]] diff --git a/doc/ja/weechat_dev.ja.adoc b/doc/ja/weechat_dev.ja.adoc index 19c983da4..b77e1c426 100644 --- a/doc/ja/weechat_dev.ja.adoc +++ b/doc/ja/weechat_dev.ja.adoc @@ -1111,18 +1111,13 @@ Git リポジトリはこの URL にあります: https://github.com/weechat/wee リクエストを使って提出することを推奨します。パッチは電子メールで送信することも可能です (`git diff` または `git format-patch` で作成してください)。 -コミットメッセージは以下の書式に従ってください (GitHub の issue を閉じる場合): +// TRANSLATION MISSING +Format of commit message is the following (with automatic close of a GitHub issue): ---- component: fix a problem (closes #123) ---- -Savannah のバグを閉じる場合: - ----- -component: fix a problem (bug #12345) ----- - _component_ には以下から 1 つ選んで記入してください: * WeeChat コア: _core_ (ルートディレクトリ、_po/_ ディレクトリ、_src/_ @@ -1134,19 +1129,18 @@ _component_ には以下から 1 つ選んで記入してください: * 英語を使ってください * 動詞の原形を使ってください -* コミットの内容がトラッカーに関するものである場合には、コミットメッセージの後にカッコで括ってその旨記載してください、書式は以下のようにしてください: -** GitHub: closes #123 -** Savannah: bug #12345, task #12345, patch #12345 +// TRANSLATION MISSING +* If commit is related to a GitHub issue, write it in parenthesis after + the message, with this format: `(issue #123)` or `(closes #123)` to close it. コミットメッセージの例: ---- -irc: add command /unquiet (closes #36) core: add callback "nickcmp" for nick comparison in buffers -irc: fix freeze when reading on socket with SSL enabled (bug #35097) -ruby: add detection of ruby version 1.9.3 in CMake +core: update Japanese translations +irc: add command /unquiet (closes #36) python: fix crash when unloading a script without pointer to interpreter -core: update Japanese translations (patch #7783) +ruby: add detection of ruby version 1.9.3 in CMake ---- [[translations]] |