unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Benjamin Rutt <brutt+news@bloomington.in.us>
Subject: Re: C-x v g going further back in time?
Date: Thu, 08 Jan 2004 17:16:03 -0500	[thread overview]
Message-ID: <wc3oeteytlo.fsf@mu.cis.ohio-state.edu> (raw)
In-Reply-To: wc3smiqyuzv.fsf@mu.cis.ohio-state.edu

Benjamin Rutt <brutt+news@bloomington.in.us> writes:

> I love C-x v g in a file managed by CVS, I can see exactly which user
> finalized which line of the file, and on which date.  This is
> invaluable for answering the question of who to ask about different
> lines of code.  However, sometimes that's not enough to find out who
> put that line of code there originally, as sometimes people make
> whitespace changes, yet C-x v g only shows the last committer of a
> line so sometimes the "whitespace changer" is not the "true author" of
> that line.  Is there any way to go back in time to see who committed a
> given line earlier in time?

Since I wrote this, I see C-x v g takes a prefix argument which can
give the revision number.  But I think it's useful also to be able to
go incrementally backwards and forwards revisions, interactively, from
within the *Annotate* buffer.  I'll look at modifying vc*.el to
support this idea.
-- 
Benjamin

  parent reply	other threads:[~2004-01-08 22:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 21:45 C-x v g going further back in time? Benjamin Rutt
2004-01-08 22:14 ` Andrew Taylor
2004-01-08 22:16 ` Benjamin Rutt [this message]
2004-01-08 22:47   ` Stefan Monnier
2004-01-21  1:02     ` Benjamin Rutt
2004-01-21  3:18       ` Stefan Monnier
2004-01-26  0:38         ` Benjamin Rutt
2004-01-26 14:28           ` Stefan Monnier
2004-01-26 15:03             ` Benjamin Rutt
2004-01-26 16:44               ` Stefan Monnier
2004-01-26 18:33               ` Stefan Monnier
2004-01-12  2:55   ` Benjamin Rutt

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=wc3oeteytlo.fsf@mu.cis.ohio-state.edu \
    --to=brutt+news@bloomington.in.us \
    /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).