From: Marco Roeland Date: Mon, 16 Jan 2006 11:33:32 GMT Subject: Re: dangling commits Message-ID: <20060116113332.GA5356@fiberbit.xs4all.nl> In-Reply-To: <43CB753D.2030706@op5.se> On Monday January 16th 2006 Andreas Ericsson wrote: > 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. Certainly. And it probably is a good testbed for testing the rebasing routines as well. But couldn't (in theory) the new "rebased" versions of blobs in the "pu" branch be first committed as the old not yet rebased version and then as the new version. Not the fact that the blobs in "pu" are constantly based on the latest master was the problem if I recollect, but the fact that blobs sometimes disappeared. In comparing this with Linus' recent explanation how git-bisect works in terms of light cones this might be understood as the inherent problems with tachyons I think... Anyway this is now solved I understand. Thanks. > >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. Ok, thanks very much for explaining. -- Marco Roeland