unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: Progress report on git-blame
Date: Sun, 26 Jan 2014 07:30:04 +0100	[thread overview]
Message-ID: <87eh3vb6hf.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvsisbn391.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 25 Jan 2014 16:48:06 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> So I'm usually just interested in a screenful of lines.  If we could
>> have a version of `C-x v g' that only does "blame" for the current
>> region, for instance, that would certainly fit my use case.
>
> One more thing: "git blame" is of no use when you're trying to see not
> "who wrote these lines when" but "who removed (and when) the lines that
> aren't there any more".

That's what the --reverse option of git blame is for.

> A "git log-and-diff" would handle that case just fine, OTOH.

git log -S "literal string" filename

is also quite helpful (it just outputs the commits where the "literal
string" appears or disappears).

-- 
David Kastrup



  parent reply	other threads:[~2014-01-26  6:30 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 14:02 RFC - cleaning up /etc Eric S. Raymond
2014-01-09 14:48 ` Samuel El-Borai
2014-01-09 15:09 ` Samuel El-Borai
2014-01-09 16:57 ` Glenn Morris
2014-01-09 17:42   ` Eric S. Raymond
2014-01-09 19:50     ` Glenn Morris
2014-01-10 14:35 ` Richard Stallman
2014-01-10 15:51   ` Eric S. Raymond
2014-01-11  7:15     ` Richard Stallman
2014-01-11 10:17       ` Eric S. Raymond
2014-01-11 18:37         ` Richard Stallman
2014-01-11 10:53       ` Ulrich Mueller
2014-01-11 20:01       ` Glenn Morris
2014-01-11 20:59         ` Eric S. Raymond
2014-01-11 21:10           ` Eli Zaretskii
2014-01-11 21:27             ` Eric S. Raymond
2014-01-12  0:07           ` Lars Magne Ingebrigtsen
2014-01-12  0:20             ` Eric S. Raymond
2014-01-12  0:37             ` David Kastrup
2014-01-12  3:51               ` Eli Zaretskii
2014-01-25  1:06               ` Progress report on git-blame (was: RFC - cleaning up /etc) David Kastrup
2014-01-25  7:34                 ` Eli Zaretskii
2014-01-25  8:59                   ` Progress report on git-blame David Kastrup
2014-01-25  9:21                     ` martin rudalics
2014-01-25  9:27                       ` David Kastrup
2014-01-25 10:12                         ` David Kastrup
2014-02-20 18:33                           ` David Kastrup
2014-01-25 18:21                     ` Lars Ingebrigtsen
2014-01-25 18:30                       ` David Kastrup
2014-01-25 18:52                       ` Óscar Fuentes
2014-01-25 18:59                         ` David Kastrup
2014-01-25 19:31                           ` Eli Zaretskii
2014-01-25 19:44                           ` Óscar Fuentes
2014-01-25 20:02                             ` David Kastrup
2014-01-25 21:45                       ` Stefan Monnier
2014-01-26 14:40                         ` Aneesh Kumar K.V
2014-01-27 14:17                           ` Stefan Monnier
2014-01-25 21:48                       ` Stefan Monnier
2014-01-25 23:03                         ` Óscar Fuentes
2014-01-26  1:48                           ` Stefan Monnier
2014-01-26 17:37                             ` Eli Zaretskii
2014-01-26 19:05                               ` Stefan Monnier
2014-01-26 19:40                                 ` Eli Zaretskii
2014-01-26 22:14                                   ` Stefan Monnier
2014-01-26  6:30                         ` David Kastrup [this message]
2014-01-26 15:07                           ` Stefan Monnier
2014-01-25  8:28                 ` David Engster
2014-01-25  9:14                   ` David Kastrup
2014-01-12  3:03             ` RFC - cleaning up /etc Stefan Monnier
2014-01-12 13:46         ` Richard Stallman
2014-01-12 19:17           ` Glenn Morris

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=87eh3vb6hf.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).