From: "Shawn O. Pearce" <spearce@spearce.org>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Mike Hommey <mh@glandium.org>, git@vger.kernel.org
Subject: Re: Blaming diffs
Date: Mon, 17 Sep 2007 00:57:04 -0400 [thread overview]
Message-ID: <20070917045704.GH3099@spearce.org> (raw)
In-Reply-To: <200709170659.15655.chriscool@tuxfamily.org>
Christian Couder <chriscool@tuxfamily.org> wrote:
> Le dimanche 16 septembre 2007, Mike Hommey a écrit :
> >
> > It seems to me there is no tool to "blame diffs", i.e. something to know
> > what commit(s) is(are) responsible for a set of changes.
>
> I don't know if that's what you are looking for but perhaps you could
> use "git bisect run". You just need to pass it a script that returns 1 when
> it finds the changes and 0 otherwise. (See git-bisect man page.)
That's very inefficient to search for something...
> Sometimes ago I sent a patch that would allow "!" after "git bisect run",
> but it seems to have been forgotten. This patch makes it possible to use:
>
> git bisect run ! grep some_stuff file1 file2...
>
> This would give you the commit where some_stuff was introduced in file1 or
> file2...
Is `git log -Ssome_stuff -- file1 file2` somehow not working for you?
--
Shawn.
next prev parent reply other threads:[~2007-09-17 4:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 16:38 Blaming diffs Mike Hommey
2007-09-16 17:05 ` Frank Lichtenheld
2007-09-16 17:16 ` Mike Hommey
2007-09-17 4:59 ` Christian Couder
2007-09-17 4:57 ` Shawn O. Pearce [this message]
2007-09-17 5:40 ` Christian Couder
2007-09-17 5:41 ` 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=20070917045704.GH3099@spearce.org \
--to=spearce@spearce.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=mh@glandium.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 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.