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: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.004 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'revision': 0.07; 'subject:Question': 0.07; 'bug.': 0.09; 'filename': 0.09; 'latter': 0.09; 'subject:Source': 0.09; 'things,': 0.09; 'wrote': 0.14; 'changes': 0.15; '(default)': 0.16; 'from:addr:python.list': 0.16; 'from:addr:tim.thechases.com': 0.16; 'from:name:tim chase': 0.16; 'hmm.': 0.16; 'ignoring': 0.16; 'refactoring': 0.16; 'tweak': 0.16; 'ignore': 0.16; 'fix': 0.17; 'wrote:': 0.18; '(the': 0.22; 'comparing': 0.24; 'text.': 0.24; 'options': 0.25; 'least': 0.26; 'header:In-Reply-To:1': 0.27; 'function': 0.29; 'chris': 0.29; 'feature': 0.29; 'lines': 0.31; 'chase': 0.31; 'trivial': 0.31; 'file': 0.32; 'option': 0.32; "i'd": 0.34; 'but': 0.35; 'really': 0.36; 'appearance': 0.36; 'charset:us-ascii': 0.36; 'skip:- 20': 0.37; 'list': 0.37; 'to:addr:python-list': 0.38; 'skip:- 10': 0.38; 'to:addr:python.org': 0.39; 'enough': 0.39; 'space': 0.40; 'blank': 0.60; 'wonderful': 0.60; 'most': 0.60; 'first': 0.61; 'show': 0.63; 'real': 0.63; 'more': 0.64; 'received:50.22': 0.84; 'subject:Control': 0.84; 'touched': 0.84 Date: Fri, 21 Mar 2014 12:54:59 -0500 From: Tim Chase To: python-list@python.org Subject: Re: Question about Source Control In-Reply-To: References: X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - boston.accountservergroup.com X-AntiAbuse: Original Domain - python.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - tim.thechases.com X-Get-Message-Sender-Via: boston.accountservergroup.com: authenticated_id: tim@thechases.com X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 31 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1395424493 news.xs4all.nl 2947 [2001:888:2000:d::a6]:36224 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:68707 On 2014-03-22 04:23, Chris Angelico wrote: > > 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".) A quick "hg -help blame" suggests that it has options to at least show the author and control the ignoring of whitespace, as well as tweak other elements: -u --user list the author (long with -v) -f --file list the filename -d --date list the date (short with -q) -n --number list the revision number (default) -c --changeset list the changeset -l --line-number show line number at the first appearance -w --ignore-all-space ignore white space when comparing lines -b --ignore-space-change ignore changes in the amount of white space -B --ignore-blank-lines ignore changes whose lines are all blank I don't see a "ignore refactoring", but I'd want to chase through those more manually.