Re: git-unpack-objects < pack file in repository doesn't work!
- From
Junio C Hamano <junkio@cox.net>
- Date
- Mar 7, 2006, 03:09 UTC
- Message-ID
- <7vlkvn54sv.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <20060307022926.GB29180@spearce.org>
Shawn Pearce <spearce@spearce.org> writes:
> I totally didn't expect that behavior. But I should have. It makes > perfect sense.
Good to hear that you two did not lose any data. I think the command should be documented as "not for interactive use without understanding what it does" ;-).
What was the reason you wanted to use it? I think we should have a wrapper command to do what you wanted to achieve, so that people do not have to run unpack-objects by hand.
One thing I _could_ think of is to explode a contaminated pack so that you can repack. For example, every time I do "git repack -a -d", the resulting pack ends up containing a couple of commits from my "pu" branch that will become dangling when I redo "pu" the next time. But then "git repack -a -d" is so inexpensive these days, without unpacking things first, I do not see the point of exploding a pack using unpack-objects in the first place.