Am 5/8/2013 18:16, schrieb Matt McClure: > That begs a follow-up question. It sounds as though Git will typically > delete unreachable objects. My team often shares links like > https://git.example.com/foo.git/log/d59051721bb0a3758f7c6ea0452bac122a377645?hp=0055e0959cd13780494fe33832bae9bcf91e4a90 > > . If I later rebase the branch containing those commits and d590517 > becomes unreachable, do I risk that link breaking when Git deletes > d590517?
Yes. When we explain 'rebase', we usually say "you make the life hard for people who build on (published) history that you later rebase". But you inconvenience not only people who build their own history on top of your outdated history, but also those who operate with (web) links into that history. > What's a good strategy for avoiding breaking those links? Do not rebase published history. -- Hannes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
