git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@fluxnic.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Brandon Casey" <drafnel@gmail.com>, "Jeff King" <peff@peff.net>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Ævar Arnfjörð" <avarab@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git auto-repack is broken...
Date: Fri, 09 Dec 2011 13:34:04 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1112091331370.2907@xanadu.home> (raw)
In-Reply-To: <7v4nx9hcmv.fsf@alter.siamese.dyndns.org>

On Fri, 9 Dec 2011, Junio C Hamano wrote:

> Nicolas Pitre <nico@fluxnic.net> writes:
> 
> > On Sat, 3 Dec 2011, Brandon Casey wrote:
> >
> >> Linus's scenario of fetching a lot of stuff that never actually makes
> >> it into the reflogs is still a valid problem.  I'm not sure that
> >> people who don't know what they are doing are going to run into this
> >> problem though.  Since he fetches a lot of stuff without ever checking
> >> it out or creating a branch from it, potentially many objects become
> >> unreferenced every time FETCH_HEAD changes.
> >
> > Maybe  FETCH_HEAD should have a reflog too?
> 
> It is a feature that the objects that were fetched for a quick peek become
> immediately unreferenced and eligible for early removal unless they are
> kept somewhere, e.g. remote tracking refs. What problem are we trying to
> solve?

This is indeed a tangential observation to the expiration delay.  I was 
just suggesting that having a reflog for FETCH_HEAD in the case when you 
fetch a branch with an explicit URL might be handy.


Nicolas

  reply	other threads:[~2011-12-09 18:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02 16:22 git auto-repack is broken Linus Torvalds
2011-12-02 16:27 ` Ævar Arnfjörð Bjarmason
2011-12-02 16:56   ` Linus Torvalds
2011-12-02 17:10     ` Jeff King
2011-12-02 17:35       ` Junio C Hamano
2011-12-02 17:45         ` Jeff King
2011-12-02 18:08           ` Junio C Hamano
2011-12-02 18:13             ` Jeff King
2011-12-03 19:42           ` Brandon Casey
2011-12-07 22:12             ` Nicolas Pitre
2011-12-07 22:53               ` Jeff King
2011-12-08  0:18                 ` Nicolas Pitre
2011-12-08  0:45                   ` Jeff King
2011-12-08  3:35                     ` Nicolas Pitre
2011-12-08  3:40                       ` Jeff King
2011-12-09 17:35               ` Junio C Hamano
2011-12-09 18:34                 ` Nicolas Pitre [this message]
2011-12-08  0:49             ` Jeff King
  -- strict thread matches above, loose matches on Subject: below --
2011-12-03  6:55 George Spelvin

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=alpine.LFD.2.02.1112091331370.2907@xanadu.home \
    --to=nico@fluxnic.net \
    --cc=avarab@gmail.com \
    --cc=drafnel@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=torvalds@linux-foundation.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 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).