From: Bagas Sanjaya <bagasdotme@gmail.com>
To: git@vger.kernel.org
Cc: worldhello.net@gmail.com, Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 3/3] po/README: document l10n conventions
Date: Thu, 11 Mar 2021 19:55:11 +0700 [thread overview]
Message-ID: <20210311125511.51152-4-bagasdotme@gmail.com> (raw)
In-Reply-To: <20210311125511.51152-1-bagasdotme@gmail.com>
Document things that l10n contributors must folow.
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
po/README | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/po/README b/po/README
index eda7edf4e6..e1a0494b17 100644
--- a/po/README
+++ b/po/README
@@ -344,3 +344,24 @@ Below are the usage examples:
po-helper.sh check XX.po
Run po-helper.sh without arguments for usage help.
+
+
+Conventions
+-----------
+
+There are some conventions that l10n contributors must follow:
+
+ 1. The subject of each commit should be prefixed with `l10n: `.
+ 2. The length of commit log title (subject) should be less than 50
+ characters, and the length of other lines (commit log body)
+ should be no more than 72 characters.
+ 3. Add "Signed-off-by" trailer to your commit log, like other
+ commits in Git. You can automatically add the trailer by
+ committing with `git commit -s`.
+ 4. Check syntax with `msgfmt` or `po-helper.sh check` before
+ committing.
+ 5. Squash trivial commits to make history clear.
+ 6. Do NOT edit files outside po/ directory.
+ 7. Other subsystems ("git-gui", "gitk", and Git itself) have their
+ own workflow. See Documentation/SubmittingPatches if you want
+ to make contributions to these subsystems.
--
2.25.1
next prev parent reply other threads:[~2021-03-11 12:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 12:55 [PATCH 0/3] po/README: document miscellaneous topics mentioned by l10n coordinator Bagas Sanjaya
2021-03-11 12:55 ` [PATCH 1/3] po/README: document PO helper Bagas Sanjaya
2021-03-12 1:32 ` Jiang Xin
2021-03-12 6:03 ` Junio C Hamano
2021-03-12 11:56 ` Bagas Sanjaya
2021-05-13 15:40 ` Jiang Xin
2021-05-27 3:11 ` Jiang Xin
2021-03-11 12:55 ` [PATCH 2/3] po/README: document "core translation" Bagas Sanjaya
2021-03-12 1:32 ` Jiang Xin
2021-03-11 12:55 ` Bagas Sanjaya [this message]
2021-03-11 13:13 ` [PATCH 3/3] po/README: document l10n conventions Bagas Sanjaya
2021-03-12 1:33 ` Jiang Xin
2021-03-12 11:47 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210311125511.51152-4-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=worldhello.net@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.