all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tom <adatgyujto@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Seeing which commits modified a range of lines?
Date: Wed, 5 Nov 2014 20:27:46 +0000 (UTC)	[thread overview]
Message-ID: <loom.20141105T211714-80@post.gmane.org> (raw)
In-Reply-To: jwvmw86vbua.fsf-monnier+gnu.emacs.help@gnu.org

Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
> 
> Oh, yes, I've been dreaming of it ever since I started using GNU Arch.
> IIUC the only tool which does provide the needed info is Git where
> you have "git log -L<begline>,<endline>:<file>".
> 

Out of the box, yes, but the point of vc is to make the life of the
user easier and hide complexities. So this functionality could be 
implmented behind the scenes.

For example, VC tools provide annotate (blame) which can tell
the last change for lines in a file. So this can be called for
a file and then the last changes for the interesting lines 
are known.

Then blame can be called for these previous versions of the file
(indicated by the changes) to find out the last changes before
that, etc. so the  implementation can walk backwards the revisions
for each line collecting the commit infos and then finally 
presenting them to the user.

So it seems the information is available via annotate (blame),
because this is provided by the VC tools, so it may not be hard
to implement in a new vc command.




  reply	other threads:[~2014-11-05 20:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.12815.1415132057.1147.help-gnu-emacs@gnu.org>
2014-11-04 22:36 ` Seeing which commits modified a range of lines? Stefan Monnier
2014-11-05 20:27   ` Tom [this message]
2014-11-05 22:31     ` Stefan Monnier
2014-11-06 20:56       ` Tom
     [not found]       ` <mailman.13069.1415307407.1147.help-gnu-emacs@gnu.org>
2014-11-06 22:42         ` Stefan Monnier
2014-11-04 20:13 Tom
2014-11-05  8:37 ` Tassilo Horn
2014-11-05 20:30   ` Tom
2014-11-06  7:13     ` Tassilo Horn
2014-11-06 20:46       ` Tom
2014-11-07  7:53         ` Thien-Thi Nguyen
2014-11-07 21:42           ` Tom
2014-11-08  8:26             ` Thien-Thi Nguyen

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=loom.20141105T211714-80@post.gmane.org \
    --to=adatgyujto@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.
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.