On Friday 26 June 2009, Junio C Hamano wrote: > Christian Couder <chriscool@xxxxxxxxxxxxx> writes: > >> If someone creates a "git decompose-octopus <commit>" command then ... > > I am afraid that misses the entire point of my discussion. > > Such a decomposed octopus would _only_ be necessary during bisection, > only when the user chooses to test two tips at once (instead of testing > one by one), _and_ only its tree is needed for that purpose. In other > words, we should be able to do this _without_ creating an extra commit, > let alone replace mechanism. But suppose the result from the bisection tells that M1 is the first bad commit, then the user will need to look at M1, and perhaps check it out or use it in other ways after the bisection is finished. So why shouldn't it be a real commit? It's not like a few more commits are a big problem as they will be reclaimed by garbage collection anyway if the replace ref is deleted. Best regards, Christian. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html