From: Stephen Bash <bash@genarts.com>
To: Jeff King <peff@peff.net>
Cc: git discussion list <git@vger.kernel.org>
Subject: Re: Git blame only current branch
Date: Mon, 12 Dec 2011 12:05:25 -0500 (EST) [thread overview]
Message-ID: <5e2440c1-8d11-4d92-b42f-14169a62ced1@mail> (raw)
In-Reply-To: <20111212165542.GA4802@sigill.intra.peff.net>
----- Original Message -----
> From: "Jeff King" <peff@peff.net>
> Sent: Monday, December 12, 2011 11:55:42 AM
> Subject: Re: Git blame only current branch
>
> On Mon, Dec 12, 2011 at 10:24:47AM -0500, Stephen Bash wrote:
>
> > I'm curious if there's a method to make git blame merge commits
> > that introduce code to the given branch rather than commits on
> > the original (topic) branch? For example:
>
> Usually when you are interested in seeing merges like this in
> git-log, you would use one of "--first-parent" or "--merges".
> However, though "git blame" takes revision arguments, it does
> its own traversal of the graph that does not respect those
> options.
My first thought was --first-parent, and was disappointed when I didn't find it in the blame documentation :) I think for my purposes --first-parent is better than --merges because there are non-merge commits on the branch(es) of interest (and thus I think the problem would become ill-posed in the --merges case).
> Modifying it to do --first-parent is pretty easy:
> ... snip ...
That's pretty simple... I'll try to do a little testing this afternoon.
Thanks!
Stephen
next prev parent reply other threads:[~2011-12-12 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e9e35956-a091-4143-8fd4-3516b54263a6@mail>
2011-12-12 15:24 ` Git blame only current branch Stephen Bash
2011-12-12 16:55 ` Jeff King
2011-12-12 17:05 ` Stephen Bash [this message]
2011-12-12 17:19 ` andreas.t.auer_gtml_37453
2011-12-13 2:07 ` Vijay Lakshminarayanan
2011-12-13 2:14 ` Jeff King
2011-12-13 5:47 ` Junio C Hamano
2011-12-13 14:09 ` Vijay Lakshminarayanan
2011-12-13 14:18 ` Frans Klaver
2011-12-13 17:25 ` Junio C Hamano
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=5e2440c1-8d11-4d92-b42f-14169a62ced1@mail \
--to=bash@genarts.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).