From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [git pull] vfs pile 2
Date: Thu, 17 Dec 2009 21:43:20 +0000 [thread overview]
Message-ID: <20091217214320.GG18217@ZenIV.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.0912171316220.15740@localhost.localdomain>
On Thu, Dec 17, 2009 at 01:22:12PM -0800, Linus Torvalds wrote:
>
>
> On Thu, 17 Dec 2009, Al Viro wrote:
> >
> > reflog had been pruned already; still no effect. Moreover, after looking
> > through the loose objects, I've found several commits that are definitely
> > reachable from master and now from your tree as well. E.g.
> > objects/ea/ff8079d4f1016a12e34ab323737314f24127dd
> > is one of those - it's a commit and it's both in mainline *and* happens
> > to be tip of master. No questions about being unreachable and AFAICS
> > no reasons whatsoever to leave it as a loose object...
>
> If you want a maximal pack, use "git repack -Adl"
Still leaves the same bunch.
> The default gc thing will stop when it hits stuff that has been packed
> already, which can leave _older_ unpacked objects unpacked. And since my
> own repo isn't always fully packed, and git will only remove local objects
> if they are available as _packed_ objects in the reference tree (ie my
> repo), you'll end up with that kind of situation.
Yeah, but why aren't they put into local pack? They _are_ new and they
definitely are referenced. The newest in the repository, as the matter
of fact.
Odd...
next prev parent reply other threads:[~2009-12-17 21:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 16:24 [git pull] vfs pile 2 Al Viro
2009-12-17 16:39 ` Linus Torvalds
2009-12-17 18:03 ` Al Viro
2009-12-17 18:16 ` Linus Torvalds
2009-12-17 18:39 ` Al Viro
2009-12-17 21:22 ` Linus Torvalds
2009-12-17 21:43 ` Al Viro [this message]
2009-12-17 21:58 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2010-10-29 13:25 [git pull] vfs, " Al Viro
2016-08-06 1:36 [git pull] vfs " Al Viro
2018-06-04 1:02 [git pull] vfs, " Al Viro
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=20091217214320.GG18217@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--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 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.