summaryrefslogtreecommitdiff
path: root/git-lost-found.sh
diff options
context:
space:
mode:
authorLibravatar Felipe Contreras <felipe.contreras@gmail.com>2012-11-28 23:24:00 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-12-03 09:57:16 -0800
commitf28e7c904ac82b0c5e43805529e7d5296fa4d13b (patch)
tree602de6ff18dc2b91a17cb747c2ae248cdeaaf783 /git-lost-found.sh
parentfast-export: don't handle uninteresting refs (diff)
downloadtgif-f28e7c904ac82b0c5e43805529e7d5296fa4d13b.tar.xz
fast-export: make sure updated refs get updated
When an object has already been exported (and thus is in the marks) it's flagged as SHOWN, so it will not be exported again, even if in a later time it's exported through a different ref. We don't need the object to be exported again, but we want the ref updated, which doesn't happen. Since we can't know if a ref was exported or not, let's just assume that if the commit was marked (flags & SHOWN), the user still wants the ref updated. IOW: If it's specified in the command line, it will get updated, regardless of whether or not the object was marked. So: % git branch test master % git fast-export $mark_flags master % git fast-export $mark_flags test Would export 'test' properly. Additionally, this fixes issues with remote helpers; now they can push refs whose objects have already been exported, and a few other issues as well. Update the tests accordingly. Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-lost-found.sh')
0 files changed, 0 insertions, 0 deletions