| 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
| ||
|
Date: Thu, 17 Dec 2009 21:43:20 +0000 From: Al Viro <viro@...IV.linux.org.uk> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: linux-kernel@...r.kernel.org Subject: Re: [git pull] vfs pile 2 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... -- 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/
Powered by blists - more mailing lists