Skip to content

Conversation

@nvie
Copy link
Contributor

@nvienvie commented Apr 13, 2016

This adds a sibling method to Repo's blame method:

Repo.blame_incremental(rev, path, **kwargs) 

This can alternatively be called using:

Repo.blame(rev, path, incremental=True) 

The main difference is that blame incremental is a bit more efficient and does not return the full file's contents, just the commits and the line number ranges. The parser is a bit more straight-forward and faster since the incremental output format is defined a little stricter.

See the test case for an example.

I've also added support for passing **kwargs to git-blame, to enable passing -C or -M to it.

nvie added 2 commits April 13, 2016 16:44
This adds a sibling method to Repo's blame method: Repo.blame_incremental(rev, path, **kwargs) This can alternatively be called using: Repo.blame(rev, path, incremental=True) The main difference is that blame incremental is a bit more efficient and does not return the full file's contents, just the commits and the line number ranges. The parser is a bit more straight-forward and faster since the incremental output format is defined a little stricter.
This can be used to pass options like -C or -M.
@ByronByron added this to the v1.0.3 - Fixes milestone Apr 14, 2016
@Byron
Copy link
Member

It seems the commits here are also included in #408 and I might have commented on it. Please feel free to reply anywhere, even though I don't think there is any reason not to merge this one.
Thanks again for your contribution !

@ByronByron merged commit 20a338f into gitpython-developers:masterApr 14, 2016
@nvienvie mentioned this pull request Apr 14, 2016
@nvienvie deleted the add-incremental-blame-support branch April 19, 2016 19:49
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@nvie@Byron