Hi, On Sun, 27 Jul 2008, Linus Torvalds wrote: > > > > Is there a way to change that default? > > > > > > Use an alias or something. > > > > This doesn't help with the graphical front ends and they only use what git > > gives them. > > And the graphical front-ends is exactly why --full-history cannot be the > default. If you mean current gitk style --full-history I agree, the problem is still that git is hiding too much history with the simplified history... > > Let's take a different example. > > No, let's not. > > Unless you can solve that _one_ example efficiently, nothing else matters. > > The above example is all you ever need. Make that one work right (and > efficiently), and everything is fine. > > And no, some random ruby code doesn't make any difference what-so-ever. > There are efficiency constraints here that make any ruby solution be > unrealistic to begin with. Why are you dismissing what I wrote without even giving it a second thought? I didn't bother with the initial example, because it's so simple, that it's no real challenge. Did I say anywhere it had to be done in ruby? All I tried was to demonstrate a possible algorithm to solve the problem. I did time the execution and compared to the time it took to extract the history it wasn't significant for such a simple script. What did I do wrong that you rebuff me based on this secondary problem (which I'm quite aware of, because it was me who mentioned in first place) and giving the primary problem (which is the missing history) no attention? If you had any questions, I'd be happy to answer them. If you think that the demonstrated algorithm doesn't work, I'd be glad to know why. If the algorithm might work, any hint what could be do done to try it for real, would be great. But I don't get any of this. Why? bye, Roman -- 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
