Shawn Pearce <spearce@xxxxxxxxxxx> writes:
> Junio C Hamano <junkio@xxxxxxx> 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
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html