Re: [PATCH] pack-objects: re-validate data we copy from elsewhere.

From: Junio C Hamano <junkio@cox.net>
Date: Sep 3, 2006, 21:00 UTC
Message-ID: <7vhczovf6m.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20060902175408.GD27826@spearce.org>

Shawn Pearce <spearce@spearce.org> writes:

Show 10 quoted lines

> Junio C Hamano <junkio@cox.net> wrote:
>
>> If rev-list had an extention that lets you say
>> 
>> 	rev-list --objects --all --unpacked=$active_pack |
>> 	pack-objects $new_pack
>
> Hmm.  Seems very reasonable actually.  :-)
>
> How do we pick the "active pack" in git-repack.sh?

I was hoping that will be a Porcelain policy issue I do not have to decide ;-).

You could introduce repack.active in .git/config that points at the latest active, make git-repack to notice and update when it updates it.

We could also just use .git/objects/pack/pack-active.{pack,idx} files. This needs some surgery to get rid of packed_git.sha1[], sha1_pack_name() and friends and have them only require .pack and .idx are linked by their basename only as was discussed in a separate thread to make it dumb-transport friendly.

-- 
VGER BF report: U 0.658122