Re: dangling commits
- From
Andreas Ericsson <ae@op5.se>
- Date
- Jan 16, 2006, 10:28 UTC
- Message-ID
- <43CB753D.2030706@op5.se>
- In-Reply-To
- <20060116101722.GB5196@fiberbit.xs4all.nl>
Marco Roeland wrote:
Show 13 quoted lines
> On Monday January 16th Junio C Hamano wrote: > > >>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"?
Since "pu" = "proposed updates" it only makes sense to keep it on top of the current master, otherwise the effort required for anyone to test it in conjunction with the latest master branch would simply be too great.
Show 5 quoted lines
> 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 since removed it from the "Pull" list, but understand that "+pu" > should do the trick. I'll retry using it one of these days.
It does. I also remember seeing lots of errors on that one when I first started with git (around 0.99b), but that was fixed quite some time ago.
-- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231