From: Rob Giardina <rob.giardina@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: does anyone have an svn version history browser
Date: Thu, 4 Dec 2008 14:01:23 -0800 (PST) [thread overview]
Message-ID: <69b1c9ba-84e6-4d72-a3a5-a3842b86db31@e1g2000pra.googlegroups.com> (raw)
In-Reply-To: mailman.1896.1228350729.26697.help-gnu-emacs@gnu.org
On Dec 3, 7:32 pm, Ian Eure <i...@digg.com> wrote:
> On Dec 3, 2008, at 12:05 PM, Rob Giardina wrote:
>
> > working in svn i often want to see the life-story of some file i'm
> > working on.
>
> > i'd like to be able to walk backwards using ediff to see the diffs
> > between version N-1 and N, a simple additional step should then show
> > me the diffs between versions N-2 and N-1, etc.
>
> I use C-x v l (vc-log). From there, you can move point to a revision
> and hit d to see the diff in that rev.
>
> - Ian
Thanks, that's fantastic.
next prev parent reply other threads:[~2008-12-04 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 20:05 does anyone have an svn version history browser Rob Giardina
2008-12-04 0:32 ` Ian Eure
[not found] ` <mailman.1896.1228350729.26697.help-gnu-emacs@gnu.org>
2008-12-04 22:01 ` Rob Giardina [this message]
2008-12-05 2:23 ` Phil Carmody
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69b1c9ba-84e6-4d72-a3a5-a3842b86db31@e1g2000pra.googlegroups.com \
--to=rob.giardina@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).