The "[command] learned [option]" construct is a really interesting way to phrase directed development effort. I'm not quite sure what the implications are, but it definitely changed the way I parsed and understood the post. "Git is getting smarter" versus "New features have been added to git."
Git 1.7.8 changes for the everyday developer
11–17 of 17 posts
Re: Git 1.7.8 changes for the everyday developer
#12[deleted]
Re: Git 1.7.8 changes for the everyday developer
#13Re: Git 1.7.8 changes for the everyday developer
#14Earlier quoted context omitted.
It's probably my most commonly-used git command, to the point where I have it aliased to "g g".
You guys should really look into http://betterthangrep.com/ :)
As amazing as ack is, it would take some effort to teach it how to grep through git history.
Re: Git 1.7.8 changes for the everyday developer
#15The "[command] learned [option]" construct is a really interesting way to phrase directed development effort. I'm not quite sure what the implications are, but it definitely changed the way I parsed and understood the post. "Git is getting smarter" versus "New features have been added to git."
We all know that Git will, one day, take over the world.
Re: Git 1.7.8 changes for the everyday developer
#16Re: Git 1.7.8 changes for the everyday developer
#17The author should try adding this to his .git/info/attributes file: *.py diff=python That should make --function-context work better on python source files.
Isn't it kind of odd that that isn't the default, given that diff=python is already built in?