From: Shengfa Lin <shengfa@google.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, nathaniel@google.com,
rsbecker@nexbridge.com, santiago@nyu.edu, shengfa@google.com
Subject: Re: [RFC PATCH 1/1] hideTimezone: add a user.hideTimezone config
Date: Fri, 2 Oct 2020 06:02:00 +0000 [thread overview]
Message-ID: <20201002060200.4073817-1-shengfa@google.com> (raw)
In-Reply-To: <xmqqpn62essa.fsf@gitster.c.googlers.com>
Thanks for the comments.
Junio C Hamano <gitster@pobox.com> writes:
>> Users requested hiding location in the world from source control
>> trail. This is an implementation to read user.hideTimezone in
>> cmd_commit and set timezone to UTC if it's true.
>>
>> Added a brief explanation of the new field in Documentation
>> and added tests for true/false and reset-author
>>
>> Signed-off-by: Shengfa Lin <shengfa@google.com>
>> ---
>> Documentation/config/user.txt | 4 ++++
>> builtin/commit.c | 5 +++++
>
> There are many ways other than running "git commit" for a commit to
> be created, including but not limited to "git merge", "git rebase",
> "git pull" (with or without "--rebase").
I overlooked on this.
>> +user.hideTimezone::
>> + Override TZ to UTC for Git commits to hide user's timezone in commit
>> + date
>
> One level of indentation in this codebase is a single HT.
>
> Unterminated sentence.
What does HT stands for? I will change the indentation to 8 spaces.
> This only affects "git commit" and no other command (which I think
> is a mistake), yet is placed in the "user.*" namespace? That does
> not make any sense. I can sort-of understand if it were called say
> "commit.useUTC" though.
I don't think this is a recommendation to implement commit.useUTC instead
since it makes more sense to support more than just the commit command.
>> diff --git a/builtin/commit.c b/builtin/commit.c
>> index 42b964e0ca..fb1cbb8a39 100644
>> --- a/builtin/commit.c
>> +++ b/builtin/commit.c
>> @@ -1569,6 +1569,11 @@ int cmd_commit(int argc, const char **argv, const char *prefix)
>> status_format = STATUS_FORMAT_NONE; /* Ignore status.short */
>> s.colopts = 0;
>>
>> + git_config(git_default_config, NULL);
>
>Declaration after statement is not tolerated in this codebase.
If I use the DEVELOPER=1 flag in config.mak and call make again, would the compiler
catches this as an error?
>> + int hide_timezone = 0;
>
> Unnecessary initialization.
>> + if (!git_config_get_bool("user.hideTimezone", &hide_timezone) && hide_timezone)
>
Is it unnecessary because I am checking the return value from git_config_get_bool so
that the uninitialized value won't be used?
>> + git add file &&
>> + # unset GIT_AUTHOR_DATE from test_tick
>> + unset GIT_AUTHOR_DATE &&
>> + TZ=Europe/Istanbul git commit -m initial &&
>> + git log -1 > output &&
>> + grep "Date: .* +0300" output
>
> Do they not have DST over there, and is it guaranteed that they will
> never have one? Would we see this test fail about half of the year,
> when timezone rules change over there in some future year? After
> all, they changed in 2016 last time, which is fairly recent.
I looked up the timezones and find one without DST without considering
the possibility of timezone rules change which would cause the test
to fail.
> This test attempts to establish the baseline, but I do not think it
> is a good idea. I think it is better *not* to unset GIT_AUTHOR_DATE
> like this. Instead, make sure it is set to some timestamp in some
> timezone that is not UTC, and the timezone of the resulting commit
> author date is in that timezone. But that must have already been
> done in basic tests on "git commit" that we honor the environment
> variable, no? Which means there is no need to add yet another extra
> baseline test here.
>
I am not sure if this test has already been done in commit basic tests.
Will remove this test.
>> +'
>> +
>> +test_expect_success 'commit date shows timezone offset +0000 even TZ setting says otherwise' '
>> + git config user.hideTimezone true &&
>> + echo test2 >> file &&
>> + git add file &&
>> + # TZ setting corresponding to -0600 or -0500 depending on DST
>> + # unset GIT_AUTHOR_DATE from test_tick
>> + unset GIT_AUTHOR_DATE &&
>> + TZ=America/Chicago git commit -m test2 &&
>
> This one is a borderline meh, compared to a test with explicit
> GIT_AUTHOR_DATE getting overridden by the configuration. It is not
> all that wrong, but I do not see a point in adding cycles to the
> already big testsuite.
>
Will remove this one as well.
next prev parent reply other threads:[~2020-10-02 6:02 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 17:14 [ISSUE] Stop accessing, storing, and sharing the user's time zone Nathaniel Manista
2019-12-05 17:31 ` Junio C Hamano
2019-12-05 17:33 ` Randall S. Becker
2019-12-05 17:43 ` Junio C Hamano
2019-12-05 17:53 ` Santiago Torres Arias
2019-12-05 18:00 ` Randall S. Becker
2020-09-30 23:21 ` [RFC PATCH 0/1] adding user.hideTimezone for setting UTC timezone Shengfa Lin
2020-09-30 23:21 ` [RFC PATCH 1/1] hideTimezone: add a user.hideTimezone config Shengfa Lin
2020-09-30 23:41 ` Junio C Hamano
2020-10-01 0:17 ` Junio C Hamano
2020-10-02 6:07 ` Shengfa Lin
2020-10-01 0:31 ` Junio C Hamano
2020-10-01 0:35 ` Junio C Hamano
2020-10-02 6:41 ` Shengfa Lin
2020-10-02 6:46 ` Shengfa Lin
2020-10-02 6:37 ` Shengfa Lin
2020-10-02 6:02 ` Shengfa Lin [this message]
2020-10-02 6:15 ` Jonathan Nieder
2020-10-02 22:32 ` Shengfa Lin
2020-10-03 4:57 ` Junio C Hamano
2020-09-30 23:55 ` Junio C Hamano
2020-10-02 6:51 ` Shengfa Lin
2020-10-01 0:05 ` Junio C Hamano
2020-10-01 2:44 ` Jonathan Nieder
2020-10-02 21:17 ` Shengfa Lin
2020-09-30 23:53 ` [RFC PATCH 0/1] adding user.hideTimezone for setting UTC timezone Junio C Hamano
2020-10-01 2:17 ` Junio C Hamano
2020-10-01 3:43 ` Jonathan Nieder
2020-10-01 15:48 ` Junio C Hamano
2020-10-08 19:49 ` Junio C Hamano
[not found] ` <CAEOYnASgxCE5NjhoSgDwyQyAmdLhw5UyFq_Fu==8q7y6uXGz6w@mail.gmail.com>
2020-10-09 16:48 ` Junio C Hamano
2020-10-02 21:56 ` Shengfa Lin
2020-10-02 22:06 ` Junio C Hamano
2020-10-03 3:50 ` Shengfa Lin
2020-10-03 4:42 ` Junio C Hamano
2020-10-03 19:53 ` brian m. carlson
2020-10-03 22:14 ` Junio C Hamano
2020-10-02 21:42 ` Shengfa Lin
2020-10-02 21:23 ` Shengfa Lin
2020-10-13 5:28 ` [WIP v2 0/2] experiment with commit option record-time-zone Shengfa Lin
2020-10-13 5:28 ` [WIP v2 1/2] Adding a record-time-zone command option for commit Shengfa Lin
2020-10-13 20:03 ` Junio C Hamano
2020-10-21 5:01 ` Shengfa Lin
2020-10-21 18:55 ` Junio C Hamano
2020-10-22 16:27 ` Junio C Hamano
2020-10-26 4:14 ` Shengfa Lin
2020-10-13 5:28 ` [WIP v2 2/2] Demonstrate failing and passing tests Shengfa Lin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201002060200.4073817-1-shengfa@google.com \
--to=shengfa@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nathaniel@google.com \
--cc=rsbecker@nexbridge.com \
--cc=santiago@nyu.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).