aboutsummaryrefslogtreecommitdiffstats
path: root/tool/prereq.status
diff options
context:
space:
mode:
authorTakashi Kokubun <takashikkbn@gmail.com>2019-06-10 22:20:00 +0900
committerTakashi Kokubun <takashikkbn@gmail.com>2019-06-10 22:35:32 +0900
commit02155da7bad37bd1c8adadd486d2d16eac7af43b (patch)
treebbd42699b63ee42402de32438fbe816032cd7610 /tool/prereq.status
parentcaa90202c9d2acbb9bce32ceebe6166c2f1de5d0 (diff)
downloadruby-02155da7bad37bd1c8adadd486d2d16eac7af43b.tar.gz
Make file2lastrev timezone consistent with git log
Using the same timezone for all commits is convenient when just looking dates in RUBY_DESCRIPTION, but usually we also check `git log` when we're interested in the order of commits. `git log` shows times in committer's timezone and forcing RUBY_RELEASE_DATE to JST makes it harder to find a corresponding commit from `git log`. Because this label is only used in development, I believe there's no strict requirement to use traditional timezone for release here. Also when building Ruby after committing from a non-JST timezone, I'd be surprised to see a strange time (in a different timezone) for my very new commit in `ruby -v`.
Diffstat (limited to 'tool/prereq.status')
0 files changed, 0 insertions, 0 deletions