2018-08-13 19:33:04 +08:00
|
|
|
#ifndef RANGE_DIFF_H
|
|
|
|
|
#define RANGE_DIFF_H
|
|
|
|
|
|
range-diff: also show the diff between patches
Just like tbdiff, we now show the diff between matching patches. This is
a "diff of two diffs", so it can be a bit daunting to read for the
beginner.
An alternative would be to display an interdiff, i.e. the hypothetical
diff which is the result of first reverting the old diff and then
applying the new diff.
Especially when rebasing frequently, an interdiff is often not feasible,
though: if the old diff cannot be applied in reverse (due to a moving
upstream), an interdiff can simply not be inferred.
This commit brings `range-diff` closer to feature parity with regard
to tbdiff.
To make `git range-diff` respect e.g. color.diff.* settings, we have
to adjust git_branch_config() accordingly.
Note: while we now parse diff options such as --color, the effect is not
yet the same as in tbdiff, where also the commit pairs would be colored.
This is left for a later commit.
Note also: while tbdiff accepts the `--no-patches` option to suppress
these diffs between patches, we prefer the `-s` (or `--no-patch`) option
that is automatically supported via our use of diff_opt_parse().
And finally note: to support diff options, we have to call
`parse_options()` such that it keeps unknown options, and then loop over
those and let `diff_opt_parse()` handle them. After that loop, we have
to call `parse_options()` again, to make sure that no unknown options
are left.
Helped-by: Thomas Gummerer <t.gummerer@gmail.com>
Helped-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-08-13 19:33:07 +08:00
|
|
|
#include "diff.h"
|
2020-07-29 04:23:39 +08:00
|
|
|
#include "strvec.h"
|
range-diff: also show the diff between patches
Just like tbdiff, we now show the diff between matching patches. This is
a "diff of two diffs", so it can be a bit daunting to read for the
beginner.
An alternative would be to display an interdiff, i.e. the hypothetical
diff which is the result of first reverting the old diff and then
applying the new diff.
Especially when rebasing frequently, an interdiff is often not feasible,
though: if the old diff cannot be applied in reverse (due to a moving
upstream), an interdiff can simply not be inferred.
This commit brings `range-diff` closer to feature parity with regard
to tbdiff.
To make `git range-diff` respect e.g. color.diff.* settings, we have
to adjust git_branch_config() accordingly.
Note: while we now parse diff options such as --color, the effect is not
yet the same as in tbdiff, where also the commit pairs would be colored.
This is left for a later commit.
Note also: while tbdiff accepts the `--no-patches` option to suppress
these diffs between patches, we prefer the `-s` (or `--no-patch`) option
that is automatically supported via our use of diff_opt_parse().
And finally note: to support diff options, we have to call
`parse_options()` such that it keeps unknown options, and then loop over
those and let `diff_opt_parse()` handle them. After that loop, we have
to call `parse_options()` again, to make sure that no unknown options
are left.
Helped-by: Thomas Gummerer <t.gummerer@gmail.com>
Helped-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-08-13 19:33:07 +08:00
|
|
|
|
2018-07-22 17:57:11 +08:00
|
|
|
#define RANGE_DIFF_CREATION_FACTOR_DEFAULT 60
|
|
|
|
|
|
2018-11-30 12:27:11 +08:00
|
|
|
/*
|
2019-11-06 01:07:23 +08:00
|
|
|
* Compare series of commits in RANGE1 and RANGE2, and emit to the
|
2018-11-30 12:27:11 +08:00
|
|
|
* standard output. NULL can be passed to DIFFOPT to use the built-in
|
|
|
|
|
* default.
|
|
|
|
|
*/
|
2018-08-13 19:33:04 +08:00
|
|
|
int show_range_diff(const char *range1, const char *range2,
|
2018-07-22 17:57:12 +08:00
|
|
|
int creation_factor, int dual_color,
|
2019-12-07 04:16:26 +08:00
|
|
|
const struct diff_options *diffopt,
|
2020-07-29 04:25:12 +08:00
|
|
|
const struct strvec *other_arg);
|
2018-08-13 19:33:04 +08:00
|
|
|
|
2021-01-28 00:37:22 +08:00
|
|
|
/*
|
|
|
|
|
* Determine whether the given argument is usable as a range argument of `git
|
|
|
|
|
* range-diff`, e.g. A..B. Note that this only validates the format but does
|
|
|
|
|
* _not_ parse it, i.e. it does _not_ look up the specified commits in the
|
|
|
|
|
* local repository.
|
|
|
|
|
*/
|
|
|
|
|
int is_range_diff_range(const char *arg);
|
|
|
|
|
|
2018-08-13 19:33:04 +08:00
|
|
|
#endif
|
