From: Yuri Khan <yuri.v.khan@gmail.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: John Wiegley <jwiegley@gmail.com>,
Jean-Christophe Helary <jean.christophe.helary@gmail.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: comparing code on different branches
Date: Tue, 4 Jul 2017 16:30:47 +0700 [thread overview]
Message-ID: <CAP_d_8VYQuLdFrLfq1187E8WtBPFNxfkMOZGHK94f9TKimFhSA@mail.gmail.com> (raw)
In-Reply-To: <87r2xw21eo.fsf@jane>
On Tue, Jul 4, 2017 at 12:53 PM, Marcin Borkowski <mbork@mbork.pl> wrote:
> BTW, is there a Magit way of doing this?
There is.
* M-x magit-find-file asks for a revision and a file name, and opens
what you ask for.
* In a buffer visiting a file in work tree, you can invoke M-x
magit-blob-previous and it will open a new buffer with the last
committed revision of the same file. Repeating M-x magit-blob-previous
(or pressing p) from that buffer opens the same file as of the
previous commit where it was modified. M-x magit-blob-next (or n)
travels in the other direction.
* In a buffer showing a diff, you can press RET on any source code
line and it will take you to that file at the relevant revision. (But
not in a diff to the working tree.)
next prev parent reply other threads:[~2017-07-04 9:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 0:53 comparing code on different branches Jean-Christophe Helary
2017-07-04 0:57 ` John Wiegley
2017-07-04 1:14 ` Jean-Christophe Helary
2017-07-04 5:17 ` Tino Calancha
2017-07-04 5:53 ` Marcin Borkowski
2017-07-04 9:30 ` Yuri Khan [this message]
2017-07-04 23:05 ` Richard Stallman
2017-07-04 23:48 ` Jean-Christophe Helary
2017-07-05 22:59 ` Richard Stallman
2017-07-05 5:54 ` Etienne Prud’homme
2017-07-05 15:55 ` Yann Hodique
2017-07-05 16:07 ` Kaushal Modi
2017-07-05 19:56 ` Etienne Prud'homme
2017-07-06 15:58 ` Richard Stallman
2017-07-13 21:48 ` Etienne Prud’homme
2017-07-04 17:51 ` Stephen Leake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP_d_8VYQuLdFrLfq1187E8WtBPFNxfkMOZGHK94f9TKimFhSA@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@gmail.com \
--cc=jwiegley@gmail.com \
--cc=mbork@mbork.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.