git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Avoiding broken Gitweb links and deleted objects

From
Johannes Sixt <j.sixt@viscovery.net>
Date
May 10, 2013, 06:07 UTC
Message-ID
<518C8EAC.6000106@viscovery.net>
In-Reply-To
<CAJELnLFrfY=-gOFEe0cJHuyT4UNjbTm8hXMxAmzmQHVbz4iEbg@mail.gmail.com>
Am 5/8/2013 18:16, schrieb Matt McClure:
Show 7 quoted lines
> 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
Previous: Matt McClureNext: Junio C Hamano
Message 3 of 14 in “Avoiding broken Gitweb links and deleted objects”
  1. Matt McClureMay 8, 2013
  2. Matt McClureMay 9, 2013
  3. Johannes SixtMay 10, 2013
  4. Junio C HamanoMay 10, 2013
  5. Johannes SixtMay 10, 2013
  6. Duy NguyenMay 10, 2013
  7. Junio C HamanoMay 10, 2013
  8. Duy NguyenMay 10, 2013
  9. Junio C HamanoMay 10, 2013
  10. Matt McClureMay 22, 2013
  11. Junio C HamanoMay 22, 2013
  12. William SwansonMay 10, 2013
  13. Matt McClureMay 22, 2013
  14. William SwansonMay 22, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.