Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!newsfeed.xs4all.nl!newsfeed1.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path: <rosuav@gmail.com>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.003
X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; '21,': 0.07; 'subject:Question': 0.07; 'bug.': 0.09; 'falls': 0.09; 'filter,': 0.09; 'git': 0.09; 'latter': 0.09; 'subject:Source': 0.09; 'things,': 0.09; 'cc:addr:python-list': 0.11; 'wrote': 0.14; 'changes': 0.15; 'bucket': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'hmm.': 0.16; 'refactoring': 0.16; 'roy': 0.16; 'ignore': 0.16; 'fix': 0.17; 'wrote:': 0.18; 'else,': 0.19; '(the': 0.22; 'import': 0.22; 'cc:addr:python.org': 0.22; 'text.': 0.24; 'cc:2**0': 0.24; 'first,': 0.26; 'least': 0.26; 'header:In-Reply-To:1': 0.27; 'function': 0.29; 'fixed': 0.29; 'feature': 0.29; "doesn't": 0.30; 'message- id:@mail.gmail.com': 0.30; "i'm": 0.30; 'lines': 0.31; 'trivial': 0.31; 'file': 0.32; 'checked': 0.32; 'option': 0.32; 'fri,': 0.33; "i'd": 0.34; 'could': 0.34; 'but': 0.35; 'received:google.com': 0.35; 'really': 0.36; 'in.': 0.36; 'two': 0.37; 'easily': 0.37; 'pm,': 0.38; 'sure': 0.39; 'enough': 0.39; 'number,': 0.60; 'wonderful': 0.60; 'most': 0.60; 'simple': 0.61; 'name': 0.63; 'real': 0.63; 'mar': 0.68; 'smith': 0.68; 'useful.': 0.68; 'hey,': 0.75; 'subject:Control': 0.84; 'touched': 0.84; 'to:none': 0.92
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=WE76X2uwMjwNx1B4t6eNUUCH5c1nNz6qgoEL5O0iDVw=; b=zlK+6jN1ZRJ6wAosx8WgAMwgK7BLGF9rk60vL2VofM5QAPPDJHoEXVvBblqsGE8/a9 IC8sIDHJhYOyYkpSnLUTyb7nm4pPH+LM7J0SKtn+6VlQkdHplPMYRu58zG1MzwFDL8UE MkbOnmzPEaILzEuT6XMARGGD/VHtSKH/cDcrZc8dXUSrbqhOZcHu+R7TMj8KTAp92d4s BlEPkRd8m0tVT3L5UnJy3ks6p82YcnxLKOrVBcB0rCk6G55e2OPH1rbQ8P/LjHgZMkck zTYRSx+79TPinrRiKSG8uZLb+6RI05IeM0+DpPhOl7Rka3EHQq9ywZE89DZcVNUn55al ERtA==
MIME-Version: 1.0
X-Received: by 10.66.164.229 with SMTP id yt5mr56095199pab.67.1395422634411; Fri, 21 Mar 2014 10:23:54 -0700 (PDT)
In-Reply-To: <roy-B841BA.08233121032014@news.panix.com>
References: <lggjcc$or$1@ger.gmane.org> <mailman.8348.1395381664.18130.python-list@python.org> <roy-B841BA.08233121032014@news.panix.com>
Date: Sat, 22 Mar 2014 04:23:54 +1100
Subject: Re: Question about Source Control
From: Chris Angelico <rosuav@gmail.com>
Cc: "python-list@python.org" <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.8365.1395422642.18130.python-list@python.org>
Lines: 23
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1395422642 news.xs4all.nl 2841 [2001:888:2000:d::a6]:50081
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:68702

On Fri, Mar 21, 2014 at 11:23 PM, Roy Smith <roy@panix.com> wrote:
> There's two things hg blame doesn't do which would be useful.
>
> First, the trivial one.  I don't want lines annotated by change number,
> I want them annotated by the name of the person who checked it in.  But,
> I'm sure that can be easily fixed with some simple post-processing
> filter, so it really falls into the bucket of "minor annoyances".
>
> The hard thing is I don't really want to know which change most recently
> touched the line of text.  I want to know who really wrote it.  It would
> be wonderful if hg were smart enough to be able to back-track through
> the change history and ignore trivial changes like whitespace,
> refactoring a function out of one file into another, etc.  That's the
> real meat and potatoes of "blame".  I want to know who I need to hit
> over the head with a clue-by-four once I fix a bug.

Hmm. 'git blame' can do both of those things, so I'd be very surprised
if 'hg blame' can't, at least with some extension(s). (The latter
feature is "git blame -w filename"; -w is a standard 'git diff' option
meaning "ignore whitespace".) But hey, if nothing else, you could
import your hg repo into git just to blame the file...

ChrisA