On Tue, Jul 29, 2008 at 04:59:01AM +0200, Roman Zippel wrote: > Right now you're giving me the choice between a crappy incomplete history > or a crappy history full of useless information. That's it? As long as > your challenge involves being compared to crappy history, I'm not > interested. If the solution should involve a switch "--correct-history" > or I have to wait for the result, I don't care, because it's the correct > history I want. As long as you're trying to sell me crappy history I'm not > buying it. > > Can we please get past this and look at what is required to produce the > correct history? You seem to be indicating here (and elsewhere in the thread) that there exists some history graph for which neither "git log" nor "git log --full-history" produces the output you want, but that there is some better output (even if it might take more time to compute). Perhaps I am just slow, but I haven't been able to figure out what that history is, or what the "correct" output should be. Can you try to state more clearly what it is you are looking for? -Peff -- 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
