From: Andy Whitcroft <apw@shadowen.org>
To: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, Petr Baudis <pasky@suse.cz>,
Luben Tuikov <ltuikov@yahoo.com>,
git@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: On blame/pickaxe
Date: Mon, 16 Oct 2006 15:15:01 +0100 [thread overview]
Message-ID: <453393E5.3020203@shadowen.org> (raw)
In-Reply-To: <200610161602.49811.Josef.Weidendorfer@gmx.de>
Josef Weidendorfer wrote:
> Hi,
>
> this blame-passing thing really looks very promising and powerful.
>
> On Monday 16 October 2006 08:43, you wrote:
>> If the user is not prepared to see code movement, pickaxe can be
>> run without -M nor -C to get the classic blame output.
>
> Another blame-passing heuristic would be very interesting for code:
> "Ignore white-space changes".
> This way, commits which only do some reindentations simply are skipped.
>
> It looks like such a thing would just be a matter of passing "-b" to
> executions of "diff" in the blame-passing algorithm.
I am thinking that that is probabally going to need to be optional, for
example python the indentation is everything to the meaning of the code.
-apw
next prev parent reply other threads:[~2006-10-16 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 1:43 On blame/pickaxe Junio C Hamano
2006-10-13 7:54 ` Junio C Hamano
2006-10-14 10:26 ` Junio C Hamano
2006-10-14 23:43 ` Junio C Hamano
2006-10-16 2:21 ` Petr Baudis
2006-10-16 6:43 ` Junio C Hamano
2006-10-16 14:02 ` Josef Weidendorfer
2006-10-16 14:15 ` Andy Whitcroft [this message]
2006-10-17 0:44 ` Petr Baudis
2006-10-21 3:20 ` Junio C Hamano
2006-10-16 23:45 ` Luben Tuikov
2006-10-17 9:03 ` 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=453393E5.3020203@shadowen.org \
--to=apw@shadowen.org \
--cc=Josef.Weidendorfer@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=ltuikov@yahoo.com \
--cc=pasky@suse.cz \
--cc=torvalds@osdl.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).