Configure the generator to compute reverse blame (history of deletes).
This method is expensive as it immediately runs a RevWalk over the history spanning the expression {@code start..end} (end being more recentthan start) and then performs the equivalent operation as {@link #push(String,AnyObjectId)} to begin blame traversal from thecommit named by {@code start} walking forwards through history until{@code end} blaming line deletions.
A reverse blame may produce multiple sources for the same result line, each of these is a descendant commit that removed the line, typically this occurs when the same deletion appears in multiple side branches such as due to a cherry-pick. Applications relying on reverse should use {@link BlameResult} as it filters these duplicate sources and onlyremembers the first (oldest) deletion.
@param start oldest commit to traverse from. The result file will be loaded from this commit's tree.
@param end most recent commit to stop traversal at. Usually an active branch tip, tag, or HEAD.
@return {@code this}
@throws IOException the repository cannot be read.