From: Matt McClure <matthewlmcclure@gmail.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Avoiding broken Gitweb links and deleted objects
Date: Thu, 9 May 2013 16:04:18 -0400 [thread overview]
Message-ID: <1912835977933437557@unknownmsgid> (raw)
In-Reply-To: <CAJELnLFrfY=-gOFEe0cJHuyT4UNjbTm8hXMxAmzmQHVbz4iEbg@mail.gmail.com>
On Wed, May 8, 2013 at 12:05 PM, Matt McClure <matthewlmcclure@gmail.com> wrote:
> On Wed, May 8, 2013 at 10:41 AM, Johannes Sixt <j.sixt@viscovery.net> wrote:
>> git gc moves unreachable objects that were packed before to the loose
>> object store, from where they can be pruned.
>
> Thanks. That was the piece I was missing. I assumed `git gc` did the opposite.
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?
What's a good strategy for avoiding breaking those links?
--
Matt McClure
http://matthewlmcclure.com
http://www.mapmyfitness.com/profile/matthewlmcclure
next prev parent reply other threads:[~2013-05-09 20:04 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 [this message]
2013-05-10 6:07 ` Johannes Sixt
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=1912835977933437557@unknownmsgid \
--to=matthewlmcclure@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.