Re: git-handler.el

[Yuri Khan <yuri.v.khan@gmail.com>]

On Sun, Aug 13, 2017 at 9:31 PM, Eli Zaretskii <eliz@gnu.org> wrote:

>> >> As a Git user, I frequently want to
>> >> browse the whole repository as of a specific revision. Use case: “Two
>> >> months ago, function foo was changed to call function bar. How did bar
>> >> look at that point?”
>> >
>> > You know, that function bar is declared in file baz.el.
>>
>> Not necessarily. It is today, but two months ago it could have resided
>> in any of baz.el, quux.el or xyzzy.el.
>
> If you don't know its file, how will you find it?

By trial and error. Find the directory at revision, L1: choose the
next most probable file, look in there. Repeat from L1 until found.

>> > So you could
>> > inspect the revisions of baz.el by looking into directory
>> > "/home/albinus/src/emacs/lisp/baz.el@@/master" (given you're interested
>> > in branch master).
>>
>> In the use case being discussed, I’m not interested in master. Or,
>> more specifically, not in its current position, and not in the whole
>> set of its commits that modify baz.el. I am interested in one specific
>> commit, say ef7a18a071, that does not modify baz.el.
>
> Then you should look inside src/emacs/lisp@@/ef7a18a071, I think.  Why
> is that a problem?

I got the impression that, in the proposed scheme, <path>@@<revision>
only shows files under <path> that are modified by the commit
<revision>. There is no problem for me if it shows *all* files under
<path> that existed at that <revision>.