On 2023-03-30 1:59 a.m., Stefan Sperling wrote:
> On Thu, Mar 30, 2023 at 02:59:06PM +1100, Mark Jamsek wrote:
of the branch):
>>
>> -c commit
>>      ...
>>      If this option is not specified, default to the work tree's current
>>      branch if invoked in a work tree, or to the repository's HEAD reference.
> 
> Subversion offers special revision keywords for such use cases.
> There is -r BASE which resolves to the base commit of a particular
> path in the working copy, whatever the base revision number happens
> to be. There is also -r WORKING which resolves to the file as it
> exists in the working copy (useful e.g. for diffing working file
> content against some other commit, a feature we do not yet support).
> 
> We could add something similar to -r BASE, such as got log -c BASE.
> Or offer a dedicated command line option for this use cases, such as
> 	got log -B [path]
> 	tog log -B [path]
> This option would of course be mutually exclusive with the -c option.

The behavior I found odd is that with the work tree rewound to a commit
with the file there on the disk, it said it couldn't identify it.

Anyway, either of those options you suggested would be consistent with
how I'd expect the tool to work intuitively and certainly a usability
improvement over copy/paste commit hashes.