diff options
| author | Jeff King <peff@peff.net> | 2014-05-20 06:49:20 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2014-05-20 18:09:03 (GMT) |
| commit | dd63f169d9381a77db469325688a2bef1a79a9e1 (patch) | |
| tree | 9f67675b9d77ce9ec6cf4003b8b57181915d86de /diff.c | |
| parent | 7bbc4e8fdb33e0a8e42e77cc05460d4c4f615f4d (diff) | |
| download | git-dd63f169d9381a77db469325688a2bef1a79a9e1.zip git-dd63f169d9381a77db469325688a2bef1a79a9e1.tar.gz git-dd63f169d9381a77db469325688a2bef1a79a9e1.tar.bz2 | |
move "--follow needs one pathspec" rule to diff_setup_done
Because of the way "--follow" is implemented, we must have
exactly one pathspec. "git log" enforces this restriction,
but other users of the revision traversal code do not. For
example, "git format-patch --follow" will segfault during
try_to_follow_renames, as we have no pathspecs at all.
We can push this check down into diff_setup_done, which is
probably a better place anyway. It is the diff code that
introduces this restriction, so other parts of the code
should not need to care themselves.
Reported-by: "Michael S. Tsirkin" <mst@redhat.com>
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'diff.c')
| -rw-r--r-- | diff.c | 3 |
1 files changed, 3 insertions, 0 deletions
@@ -3317,6 +3317,9 @@ void diff_setup_done(struct diff_options *options) options->output_format = DIFF_FORMAT_NO_OUTPUT; DIFF_OPT_SET(options, EXIT_WITH_STATUS); } + + if (DIFF_OPT_TST(options, FOLLOW_RENAMES) && options->pathspec.nr != 1) + die(_("--follow requires exactly one pathspec")); } static int opt_arg(const char *arg, int arg_short, const char *arg_long, int *val) |