git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: David Christensen <david@endpoint.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	pi song <pi.songs@gmail.com>, Junio C Hamano <gitster@pobox.com>
Subject: Re: Feature suggestion: git grep --blame
Date: Sat, 20 Jun 2009 20:19:10 +0200	[thread overview]
Message-ID: <4A3D281E.4070500@lsrfire.ath.cx> (raw)
In-Reply-To: <B13F8D3F-E69B-49BA-9B81-27DF19E33A43@endpoint.com>

David Christensen schrieb:
> Hey folks,
> 
> It's occurred to me on several occasions that a useful output option for
> `git grep` would be to prefix lines with the same commit/author/date
> annotation that `git blame` shows when viewing an individual file.  I
> didn't find anything myself with a quick google search so I was
> wondering if anyone a) has a recipe for this either with a trivial
> command alias (I couldn't come up with one myself), b) know if this has
> been done/attempted before, or c) have a reason why this is a really
> stupid idea? :-)

This is a very good idea -- so good, in fact, that Pi Song sent patches
to implement it a quarter ago.  There were a few issues which prevented
them from being merged unchanged.  Junio merged an initial cleanup patch
into pu instead ("blame.c: start libifying the blame infrastructure",
97926c6c).  Work on the remaining parts seems to have stalled, though.
Pi Song?

René

      reply	other threads:[~2009-06-20 18:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-20 15:29 Feature suggestion: git grep --blame David Christensen
2009-06-20 18:19 ` René Scharfe [this message]

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=4A3D281E.4070500@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=david@endpoint.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pi.songs@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.
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 NNTP newsgroup(s).