unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Bob Rogers <rogers-emacs@rgrjr.dyndns.org>
Cc: Thierry Volpiatto <thierry.volpiatto@gmail.com>,
	"Stephen J. Turnbull" <stephen@xemacs.org>,
	Dan Nicolaescu <dann@ics.uci.edu>,
	emacs-devel@gnu.org
Subject: Re: limit the number of log entries displayed by C-x v l
Date: Mon, 23 Nov 2009 00:17:46 -0500	[thread overview]
Message-ID: <jwvskc5zuy2.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <19210.1600.43351.317882@rgr.rgrjr.com> (Bob Rogers's message of "Sun, 22 Nov 2009 22:49:20 -0500")

> Here's a non-backend-specific hack for C-n and C-p in vc-annotate-mode
> that keeps any log-view-mode buffer displayed on the same frame in sync
> to the same revision.  A post-command-hook solution might be more
> thorough, though (handling C-s, e.g.), but is this in the direction of
> what you had in mind?

Not really.  I want to give a range of lines BEG..END and then get
a list of patches going backward in time showing all the commits that
ended up (directly or indirectly) with generating those lines.
So it will give me an information akin to (tho not in prose) "those
lines were changed in r1834 by changing indentation, before that r1498
renamed foo to bar, before that r1244 extended the code to handle one
more case, and finally r1022 is the one change that really introduced
the core behavior of those lines (and then it'll keep telling me more
things but I won't care about them)".

I do it in a backend-independent way by hand, in the following way:
1- start at REV=latest revision
2- vc-annotate REV
3- get the diff and log of the lines
4- set REV to the revision prior to the one that changed those lines and
   go back to 2.


        Stefan




  reply	other threads:[~2009-11-23  5:17 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12 23:19 limit the number of log entries displayed by C-x v l Dan Nicolaescu
2009-11-13  1:18 ` Stefan Monnier
2009-11-13  2:21   ` Dan Nicolaescu
2009-11-13  3:19     ` Stefan Monnier
2009-11-13  5:02       ` Dan Nicolaescu
2009-11-13 14:10         ` Stefan Monnier
2009-11-15 20:55           ` Dan Nicolaescu
2009-11-15 21:34             ` Chong Yidong
2009-11-16  9:40             ` Dan Nicolaescu
2009-11-16 14:22               ` Stefan Monnier
2009-11-16 15:10                 ` Dan Nicolaescu
2009-11-16 15:41                   ` Stefan Monnier
2009-11-16 20:40                     ` Dan Nicolaescu
2009-11-17 13:44           ` Dan Nicolaescu
2009-11-17 19:54             ` Stefan Monnier
2009-11-18 18:19               ` Dan Nicolaescu
2009-11-19  0:52                 ` Stefan Monnier
2009-11-19  7:23                   ` Thierry Volpiatto
2009-11-20  6:59                     ` Dan Nicolaescu
2009-11-20  7:19                       ` Thierry Volpiatto
2009-11-20 14:11                       ` Stefan Monnier
2009-11-20 15:26                         ` Dan Nicolaescu
2009-11-21  4:27                           ` Stephen J. Turnbull
2009-11-22 20:12                             ` Stefan Monnier
2009-11-22 23:02                               ` Štěpán Němec
2009-11-23  2:29                                 ` Stefan Monnier
2009-11-23  3:49                                   ` Bob Rogers
2009-11-23  5:17                                     ` Stefan Monnier [this message]
2009-11-22 20:10                           ` Stefan Monnier
2009-12-06 17:43                   ` Dan Nicolaescu
2009-12-07  2:12                     ` Stefan Monnier
2009-11-13  6:59     ` Giorgos Keramidas
2009-11-14 10:10 ` Alfred M. Szmidt
2009-11-14 23:29   ` Richard Stallman
2009-11-14 23:34     ` Andreas Schwab
2009-11-15 22:38       ` Richard Stallman
2009-11-15 22:52         ` Andreas Schwab
2009-11-17  7:56           ` Richard Stallman

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=jwvskc5zuy2.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=rogers-emacs@rgrjr.dyndns.org \
    --cc=stephen@xemacs.org \
    --cc=thierry.volpiatto@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).