Skip to content

G
git2
Commit 687da95e by Antonin Delpeuch
Options

blame example: Fix support for line range in CLI 

The -L option announced by the CLI was ignored so far.
parent 4939fa74
Showing with 4 additions and 0 deletions
examples/blame.c
...@@ -47,6 +47,10 @@ int lg2_blame(git_repository *repo, int argc, char *argv[]) ...@@ -47,6 +47,10 @@ int lg2_blame(git_repository *repo, int argc, char *argv[])
if (o.M) blameopts.flags |= GIT_BLAME_TRACK_COPIES_SAME_COMMIT_MOVES; if (o.M) blameopts.flags |= GIT_BLAME_TRACK_COPIES_SAME_COMMIT_MOVES;
if (o.C) blameopts.flags |= GIT_BLAME_TRACK_COPIES_SAME_COMMIT_COPIES; if (o.C) blameopts.flags |= GIT_BLAME_TRACK_COPIES_SAME_COMMIT_COPIES;
if (o.F) blameopts.flags |= GIT_BLAME_FIRST_PARENT; if (o.F) blameopts.flags |= GIT_BLAME_FIRST_PARENT;
if (o.start_line && o.end_line) {
blameopts.min_line = o.start_line;
blameopts.max_line = o.end_line;
}
/** /**
* The commit range comes in "committish" form. Use the rev-parse API to * The commit range comes in "committish" form. Use the rev-parse API to
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment