aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNao Ueda <nao.uedder@gmail.com>2021-02-06 10:59:14 +0900
committerNao Ueda <nao.uedder@gmail.com>2021-02-06 11:02:43 +0900
commitfa07b0e4d65a14a01d7494d2261b2868e587deee (patch)
tree6d03ed537e52b7dc61cbc5c5fc9ef0a786ee5de8
parente9971c86798b2f57987c6f77860375797689f959 (diff)
downloadgit-file-changed-time-getter-fa07b0e4d65a14a01d7494d2261b2868e587deee.tar.gz
git-file-changed-time-getter-fa07b0e4d65a14a01d7494d2261b2868e587deee.tar.bz2
git-file-changed-time-getter-fa07b0e4d65a14a01d7494d2261b2868e587deee.zip
add a NOTE section to README
-rw-r--r--README.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/README.md b/README.md
index 2965917..84caa55 100644
--- a/README.md
+++ b/README.md
@@ -13,3 +13,7 @@ On basically git concept, objects that have time state (_committer committed tim
Probably this concept is itself intentionally, so **this wrapper script is expected to use in some cases as a workaround**.
So if possible, you should consider another approach to the case before using this wrapper script.
+
+## NOTE
+- This script prints timestamps where each blob object has changed between trees that are traced by commit-objects history. So if a file is changed in a branch and merged to the main branch with merge commit (e.g. using `--no-ff` option), **the timestamp comes from the merge commit**.
+- All timestamps are _committer-commit_ timestamps, not _author-commit_ timestamps.