From: Jakub Narebski <jnareb@gmail.com>
To: Ian Hilt <Ian.Hilt@gmx.com>
Cc: Mircea Bardac <dev@bardac.net>, git@vger.kernel.org
Subject: Re: git blame for a commit
Date: Mon, 23 Jun 2008 18:29:21 +0200 [thread overview]
Message-ID: <200806231829.22004.jnareb@gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0806231149470.27742@sys-0.hiltweb.site>
On Mon, 23 Jun 2008, Ian Hilt wrote:
> On Mon, 23 Jun 2008 at 3:01am -0700, Jakub Narebski wrote:
>
> > I think you could script it using "git diff", and "git blame -L m,n",
> > where line ranges would be calculated from git diff header for
> > post-image, or both pre-image and post-image (in the case of deletions).
>
> Maybe I'm missing something, but I thought git-blame only worked with
> the files in the Git working directory. Therefore, if a file had been
> deleted it would not be reachable with git-blame, whether you diff'ed
> the pre- and post-image or not.
You can give blame the revision to start blaming from; that's what
I meant the "pre-image" blame (staring from parent revision).
I'm not that sure if it is the best solution...
--
Jakub Narebski
Poland
prev parent reply other threads:[~2008-06-23 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 22:32 git blame for a commit Mircea Bardac
2008-06-23 3:40 ` Ian Hilt
2008-06-23 9:04 ` Mircea Bardac
2008-06-23 10:01 ` Jakub Narebski
2008-06-23 15:55 ` Ian Hilt
2008-06-23 16:29 ` Jakub Narebski [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=200806231829.22004.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Ian.Hilt@gmx.com \
--cc=dev@bardac.net \
--cc=git@vger.kernel.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.
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).