On Fri, Jan 20, 2012 at 10:09:51AM -0800, Junio C Hamano wrote: > > Yes, thank you for finding that out. X is actually v5.15.4-109-g3ea0c58 > > and since there was a long timespan between the start of the development > > of the code and the merge (May-Nov), the gitk presentation got a bit > > complex to read. > > (This is somewhat off-topic, so Andreas is on Cc: and the list is on To:) > > I doubt --simplify-by-decoration alone would make it easier to view such a > complex and long history, but I wonder if we can use the same logic to > help users in a case like this. Instead of only keeping tagged versions in > the result to show topology, perhaps we can allow the user to feed a list > of "key points in history" as command line arguments and apply the same > kind of simplification to help visualizing the topology? This is something I think I've wanted in the past. But unfortunately, I can't remember the exact details, so I'm not sure how workable it would have been. In particular, how painful is it in practice to come up with the list of "key points" to make the graph sensible? So I'll add my vague "yeah, that sounds good" and try to pay attention next time the situation comes up as to whether such a feature would actually help in practice. -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