Thread (2 messages) flat view 2 messages, 2 authors, 2016-06-15

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

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:39

Shawn Pearce [off-list ref] writes:
Junio C Hamano [off-list ref] wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help