From 1ff6e2449ad9593de45cc452f263f8be18a92c3d Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Fri, 2 Mar 2018 09:38:18 -0800 Subject: [PATCH] =?UTF-8?q?*=20CONTRIBUTING:=20Mention=20=E2=80=98git=20bl?= =?UTF-8?q?ame=E2=80=99.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- CONTRIBUTING | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING b/CONTRIBUTING index 716f32b..0cfc77f 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -25,7 +25,8 @@ justification. Citations should use https: URLs if available. Please submit changes against either the latest release in or the master branch of the development -repository. If you use Git the following workflow may be helpful: +repository. The latter is preferred. If you use Git the following +workflow may be helpful: * Copy the development repository. @@ -42,6 +43,12 @@ repository. If you use Git the following workflow may be helpful: git checkout -b mybranch + * Sleuth by using 'git blame'. For example, when fixing data for + Africa/Sao_Tome, if the command 'git blame africa' outputs a line + '2951fa3b (Paul Eggert 2018-01-08 09:03:13 -0800 1068) Zone + Africa/Sao_Tome 0:26:56 - LMT 1884', commit 2951fa3b should + provide some justification for the 'Zone Africa/Sao_Tome' line. + * Edit source files. Include commentary that justifies the changes by citing reliable sources. @@ -67,6 +74,9 @@ repository. If you use Git the following workflow may be helpful: git send-email master + For an archived example of such an email, see + . + * Start anew by getting current with the master branch again (the second step above). -- 2.14.3