Re: Unexpected behavior with :/ references

2018-07-09 Thread William Chargin
Yep, I agree with your analysis. I'd be happy to test and commit this, probably later today. Thanks for your input, and for the patch! Best, WC

Re: Unexpected behavior with :/ references

2018-07-09 Thread Jeff King
On Sun, Jul 08, 2018 at 10:13:12PM -0700, William Chargin wrote: > After further investigation, it appears that ":/foo" indeed resolves to > the commit with message "foobar" (in the above example) if the commits > are not all created at the same time: e.g., by adding `sleep 1` between > the commit

Re: Unexpected behavior with :/ references

2018-07-08 Thread William Chargin
After further investigation, it appears that ":/foo" indeed resolves to the commit with message "foobar" (in the above example) if the commits are not all created at the same time: e.g., by adding `sleep 1` between the commit commands, or exporting `GIT_AUTHOR_DATE`. This leaves only the question

Unexpected behavior with :/ references

2018-07-08 Thread William Chargin
Hello, I'm experiencing strange behavior with :/ references, which seems to be inconsistent with the explanation in the docs on two counts. First, sometimes the matched commit is not the youngest. Second, some commits cannot be found at all, even if they are reachable from HEAD. Here is a script