From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: git-handler.el Date: Sun, 13 Aug 2017 17:31:58 +0300 Message-ID: <83a833ilnl.fsf@gnu.org> References: <87eftk9uxe.fsf@bernoul.li> <87zic7ze06.fsf_-_@detlef> <87d192aold.fsf@bernoul.li> <87o9rmiems.fsf@detlef> <877ey9cb9l.fsf@bernoul.li> <87inhstx2y.fsf@detlef> <87wp67suba.fsf@detlef> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1502634798 6876 195.159.176.226 (13 Aug 2017 14:33:18 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 13 Aug 2017 14:33:18 +0000 (UTC) Cc: emacs-devel@gnu.org, jonas@bernoul.li, michael.albinus@gmx.de, dgutov@yandex.ru To: Yuri Khan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Aug 13 16:33:10 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dgtwz-0001Lp-Pj for ged-emacs-devel@m.gmane.org; Sun, 13 Aug 2017 16:33:09 +0200 Original-Received: from localhost ([::1]:56076 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dgtx6-00050S-58 for ged-emacs-devel@m.gmane.org; Sun, 13 Aug 2017 10:33:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40695) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dgtw0-0004zf-Pa for emacs-devel@gnu.org; Sun, 13 Aug 2017 10:32:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dgtvx-0001TC-Kl for emacs-devel@gnu.org; Sun, 13 Aug 2017 10:32:08 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:58770) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dgtvx-0001T8-If; Sun, 13 Aug 2017 10:32:05 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3312 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dgtvx-0004MF-0E; Sun, 13 Aug 2017 10:32:05 -0400 In-reply-to: (message from Yuri Khan on Sun, 13 Aug 2017 17:08:35 +0700) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:217509 Archived-At: > From: Yuri Khan > Date: Sun, 13 Aug 2017 17:08:35 +0700 > Cc: Jonas Bernoulli , Dmitry Gutov , > Emacs developers > > On Sun, Aug 13, 2017 at 4:14 PM, Michael Albinus 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? > > 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 never use find-file interactively except to create a new file or > jump to a directory on a remote server (via Tramp). > * I navigate from a file to its containing directory or from a > directory to its parent using dired-jump, and from a directory to a > file using dired-find-file. This just means Dired will need to be taught about these special file names.