Re: dangling commits

From: Marco Roeland <marco.roeland@xs4all.nl>
Date: Jan 16, 2006, 10:17 UTC
Message-ID: <20060116101722.GB5196@fiberbit.xs4all.nl>
In-Reply-To: <7vr778wmj3.fsf@assigned-by-dhcp.cox.net>

On Monday January 16th Junio C Hamano wrote:

Show 5 quoted lines

> Even when you use git native protocol, the objects the initial
> clone gives you are kept packed, so when I rewind and rebuild
> "pu" to make some of these objects orphaned, they will stay in
> the pack the initial clone gave you.  Unpack+repack is needed to
> get rid of them.

Thanks very much for explaining. It makes sense now.

Does it bring many advantages for you to keep rebasing "pu"? I started out following that branch long ago (well in git reckoning anyway) but got very scared each time I got a bunch of "errors" on that one. I even recloned a couple of times to get it "clean" again, until I understood from the mailing-list that the rebasing was the cause, not something I did. I since removed it from the "Pull" list, but understand that "+pu" should do the trick. I'll retry using it one of these days.

-- 
Marco Roeland