linux-kernel - Re: [git pull] vfs pile 2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.0912171350540.15740@localhost.localdomain>
Date:	Thu, 17 Dec 2009 13:58:16 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Al Viro <viro@...IV.linux.org.uk>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [git pull] vfs pile 2


On Thu, 17 Dec 2009, Al Viro wrote:
> 
> 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...

Hmm. It seems to be the same objects that are unpacked in my repo. What 
happens is probably that git doesn't want to pack them, because they are 
available in the alternates, but then also doesn't want to prune them, 
because they aren't available in a _pack_ in the alternate.

That does look like something we migth decide to want to change in git. 
Maybe. 

But I repacked my repo, just so that you can get your "no loose objects" 
situation you want ;)

		Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/