| commit | 15b76c1fb3ab013b99498c9dca333aaa4808927e | |
| author | Xiaolong Ye <xiaolong.ye@intel.com> | |
| Mon, 4 Jun 2018 15:05:43 +0000 (4 23:05 +0800) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 19 Jun 2018 18:36:41 +0000 (19 11:36 -0700) | ||
| tree | 3332cfcfc2de566fd86a0ac2890358b5f466054a | treesnapshot (tar.gz zip) |
| parent | a42a58d7b62cc1d6301440e81a83feed9d7c118c | commitdiff |
format-patch: clear UNINTERESTING flag before prepare_bases
When users specify the commit range with 'Z..C' pattern for format-patch, all
the parents of Z (including Z) would be marked as UNINTERESTING which would
prevent revision walk in prepare_bases from getting the prerequisite commits,
thus `git format-patch --base <base_commit_sha> Z..C` won't be able to generate
the list of prerequisite patch ids. Clear UNINTERESTING flag with
clear_object_flags solves this issue.
Reported-by: Eduardo Habkost <ehabkost@redhat.com>
Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com>
Reviewed-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
When users specify the commit range with 'Z..C' pattern for format-patch, all
the parents of Z (including Z) would be marked as UNINTERESTING which would
prevent revision walk in prepare_bases from getting the prerequisite commits,
thus `git format-patch --base <base_commit_sha> Z..C` won't be able to generate
the list of prerequisite patch ids. Clear UNINTERESTING flag with
clear_object_flags solves this issue.
Reported-by: Eduardo Habkost <ehabkost@redhat.com>
Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com>
Reviewed-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin/log.c | diffblobblamehistory | |
| t/t4014-format-patch.sh | diffblobblamehistory |