Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #68707

Re: Question about Source Control

Date 2014-03-21 12:54 -0500
From Tim Chase <python.list@tim.thechases.com>
Subject Re: Question about Source Control
References <lggjcc$or$1@ger.gmane.org> <mailman.8348.1395381664.18130.python-list@python.org> <roy-B841BA.08233121032014@news.panix.com> <CAPTjJmpBFCUfkkgcobAc=jMFObZDh4=7HEaFEHz=M0vbW1t28Q@mail.gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.8366.1395424493.18130.python-list@python.org> (permalink)

Show all headers | View raw


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.

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: Question about Source Control Cameron Simpson <cs@zip.com.au> - 2014-03-21 17:00 +1100
  Re: Question about Source Control Roy Smith <roy@panix.com> - 2014-03-21 08:23 -0400
    Re: Question about Source Control Chris Angelico <rosuav@gmail.com> - 2014-03-22 04:23 +1100
    Re: Question about Source Control Tim Chase <python.list@tim.thechases.com> - 2014-03-21 12:54 -0500
    Re: Question about Source Control Tim Chase <python.list@tim.thechases.com> - 2014-03-21 12:59 -0500
    Re: Question about Source Control Cameron Simpson <cs@zip.com.au> - 2014-03-22 08:32 +1100
    Re: Question about Source Control Chris Angelico <rosuav@gmail.com> - 2014-03-22 09:17 +1100

csiph-web