From: vvs
To: Git for human beings
Cc: [email protected] ; [email protected] ; [email protected]
Sent: Saturday, April 22, 2017 6:33 PM
Subject: Re: [git-users] Undocumented reset behavior
On Saturday, April 22, 2017 at 7:57:40 PM UTC+3, Philip Oakley wrote:
Modify: 2017-04-22 16:47:19.437500000 +0100
Modify: 2017-04-22 16:47:29.640625000 +0100
So in both these cases, the test simplification appears to result in
identical output (unless I missed something - could easily happen)
Yes, you missed the changed timestamp. I have aligned both A and B for better
view.
The image didn't get through..
Thanks for highlighting! my brain isn't fully clear from a head cold!
So, at the final stat:
Option A (git reset @{1}; git reset --hard)
Modify: 2017-04-22 16:43:47.562500000 +0100
Change: 2017-04-22 16:43:47.562500000 +0100
Birth: 2017-04-22 16:43:47.562500000 +0100
while
Option B (git reset --hard @{1})
Modify: 2017-04-22 16:47:29.640625000 +0100
Change: 2017-04-22 16:47:29.640625000 +0100
Birth: 2017-04-22 16:47:19.437500000 +0100
Option B has an updated timestamp, which triggers the makefile response.
Somewhere there is a classic Linus response about timestamps being
irrelevancies for a true VCS (he says the same for renames, etc.) (SO answer
with discussion & links http://stackoverflow.com/a/1964508/717355)
On the main list thare is a similar "issue" [1] regarding the expectation for
`git checkout`, and importantly (for me) these collected views regarding the
"Git Data Protection and Management Principles" is not within the Git
documentation.
philip
[1] https://public-inbox.org/git/[email protected]/
--
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
