A fun thing is that the full gitrevisions syntax used by `rev-parse` is supported many places on GitHub where you would normally put an object id or ref name.

A fun thing is that the full gitrevisions syntax used by `rev-parse` is supported many places on GitHub where you would normally put an object id or ref name. For example, https://github.com/git/git/tree/master@{5.years.ago} https://github.com/git/git/tree/master@{5.years.ago} Note that this uses the reflog which means that it won’t work in some situations (branch renames, entries rolled off the end of the log, etc)