summaryrefslogtreecommitdiff
path: root/Documentation/howto/recover-corrupted-object-harder.txt
diff options
context:
space:
mode:
authorXiaolong Ye <xiaolong.ye@intel.com>2018-06-04 15:05:43 (GMT)
committerJunio C Hamano <gitster@pobox.com>2018-06-19 18:36:41 (GMT)
commit15b76c1fb3ab013b99498c9dca333aaa4808927e (patch)
tree3332cfcfc2de566fd86a0ac2890358b5f466054a /Documentation/howto/recover-corrupted-object-harder.txt
parenta42a58d7b62cc1d6301440e81a83feed9d7c118c (diff)
downloadgit-15b76c1fb3ab013b99498c9dca333aaa4808927e.zip
git-15b76c1fb3ab013b99498c9dca333aaa4808927e.tar.gz
git-15b76c1fb3ab013b99498c9dca333aaa4808927e.tar.bz2
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>
Diffstat (limited to 'Documentation/howto/recover-corrupted-object-harder.txt')
0 files changed, 0 insertions, 0 deletions