Fossil SCM
Small clarity tweaks to the list of weaknesses for "git checkout master@{2020-03-17}" in the gitusers doc.
Commit
ed7c2c1b685c816c552bc525fe737cd911a6afb33a0a3c88b8a767d627e0a0b6
Parent
9199f77119cc7e7…
1 file changed
+7
-6
+7
-6
| --- www/gitusers.md | ||
| +++ www/gitusers.md | ||
| @@ -795,18 +795,19 @@ | ||
| 795 | 795 | 1. It’s a bit cryptic. Leave off the refname or punctuation, and it |
| 796 | 796 | means something else. You cannot simplify the cryptic incantation in |
| 797 | 797 | the typical use case. |
| 798 | 798 | |
| 799 | 799 | 2. A date string in Git without a time will be interpreted as |
| 800 | - “[at localtime on that date][gapxd],” so the command means something | |
| 801 | - different from one second to the next! If there are multiple commits | |
| 802 | - on that date, that command can give different results depending on | |
| 803 | - the time of day you run it. | |
| 800 | + “[at the local wall clock time on the given date][gapxd],” so the | |
| 801 | + command means something different from one second to the next. This | |
| 802 | + can be a problem if there are multiple commits on that date, because | |
| 803 | + the command will give diffferent results depending on the time of | |
| 804 | + day you run it. | |
| 804 | 805 | |
| 805 | 806 | 3. It gives misleading output if there is no close match for the date |
| 806 | - in target commit in the local [reflog]. On a fresh clone, the reflog | |
| 807 | - is empty, and even on a well-established clone, Git [automatically | |
| 807 | + in the local [reflog]. It starts out empty after a fresh clone, and | |
| 808 | + while it does build up as you use that clone, Git [automatically | |
| 808 | 809 | prunes][gle] the reflog to 90 days of history by default. This means |
| 809 | 810 | the command above can give different results from one machine to the |
| 810 | 811 | next, or even from one day to the next on the same clone. |
| 811 | 812 | |
| 812 | 813 | The command won’t fail outright if the reflog can’t resolve the |
| 813 | 814 |
| --- www/gitusers.md | |
| +++ www/gitusers.md | |
| @@ -795,18 +795,19 @@ | |
| 795 | 1. It’s a bit cryptic. Leave off the refname or punctuation, and it |
| 796 | means something else. You cannot simplify the cryptic incantation in |
| 797 | the typical use case. |
| 798 | |
| 799 | 2. A date string in Git without a time will be interpreted as |
| 800 | “[at localtime on that date][gapxd],” so the command means something |
| 801 | different from one second to the next! If there are multiple commits |
| 802 | on that date, that command can give different results depending on |
| 803 | the time of day you run it. |
| 804 | |
| 805 | 3. It gives misleading output if there is no close match for the date |
| 806 | in target commit in the local [reflog]. On a fresh clone, the reflog |
| 807 | is empty, and even on a well-established clone, Git [automatically |
| 808 | prunes][gle] the reflog to 90 days of history by default. This means |
| 809 | the command above can give different results from one machine to the |
| 810 | next, or even from one day to the next on the same clone. |
| 811 | |
| 812 | The command won’t fail outright if the reflog can’t resolve the |
| 813 |
| --- www/gitusers.md | |
| +++ www/gitusers.md | |
| @@ -795,18 +795,19 @@ | |
| 795 | 1. It’s a bit cryptic. Leave off the refname or punctuation, and it |
| 796 | means something else. You cannot simplify the cryptic incantation in |
| 797 | the typical use case. |
| 798 | |
| 799 | 2. A date string in Git without a time will be interpreted as |
| 800 | “[at the local wall clock time on the given date][gapxd],” so the |
| 801 | command means something different from one second to the next. This |
| 802 | can be a problem if there are multiple commits on that date, because |
| 803 | the command will give diffferent results depending on the time of |
| 804 | day you run it. |
| 805 | |
| 806 | 3. It gives misleading output if there is no close match for the date |
| 807 | in the local [reflog]. It starts out empty after a fresh clone, and |
| 808 | while it does build up as you use that clone, Git [automatically |
| 809 | prunes][gle] the reflog to 90 days of history by default. This means |
| 810 | the command above can give different results from one machine to the |
| 811 | next, or even from one day to the next on the same clone. |
| 812 | |
| 813 | The command won’t fail outright if the reflog can’t resolve the |
| 814 |