From: Johannes Sixt <j.sixt@viscovery.net>
To: Matt McClure <matthewlmcclure@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Avoiding broken Gitweb links and deleted objects
Date: Fri, 10 May 2013 08:07:40 +0200 [thread overview]
Message-ID: <518C8EAC.6000106@viscovery.net> (raw)
In-Reply-To: <CAJELnLFrfY=-gOFEe0cJHuyT4UNjbTm8hXMxAmzmQHVbz4iEbg@mail.gmail.com>
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
next prev parent reply other threads:[~2013-05-10 6:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 16:16 Avoiding broken Gitweb links and deleted objects Matt McClure
2013-05-09 20:04 ` Matt McClure
2013-05-10 6:07 ` Johannes Sixt [this message]
2013-05-10 6:37 ` Junio C Hamano
2013-05-10 7:03 ` Johannes Sixt
2013-05-10 7:04 ` Duy Nguyen
2013-05-10 7:16 ` Junio C Hamano
2013-05-10 10:33 ` Duy Nguyen
2013-05-10 16:22 ` Junio C Hamano
2013-05-22 13:25 ` Matt McClure
2013-05-22 17:39 ` Junio C Hamano
2013-05-10 7:34 ` William Swanson
2013-05-22 13:32 ` Matt McClure
2013-05-22 15:41 ` William Swanson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=518C8EAC.6000106@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=matthewlmcclure@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).