On Tue, 12 Feb 2008, James Bottomley wrote: > > Yes, this is exactly the feature I'm looking for. It would allow the > downstream users of a rebased tree to rebase themselves correctly. > > All the information about the rebase is in the reflog ... it can't be > too difficult to pass it through on a pull and allow the downstream tree > to do the right thing. Guys, you simply have no idea what you're talking about. Those downstream trees can have done things themselves. They *depended* on the state you gave them. You can't just say "oops, I lied, this is the state you should have used, now it's _your_ mess to sort out". OF COURSE it's what you'd like to use - it absolves you of any and all actual responsibility. But dammit, that's not what anybody else wants than the irresponsible person who cannot be bothered to stand up for his work! If you're not confident enough about your work, don't push it out! It's that simple. Pushing out to a public branch is a small "release". Have the f*cking back-bone to be able to stand behind what you did! Linus - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html