On Tue, Jul 29, 2008 at 2:59 PM, Roman Zippel <zippel@xxxxxxxxxxxxxx> wrote: > Can we please get past this and look at what is required to produce the > correct history? Roman - correct is --full-history -- any simplification that makes it easy on your eyes *is* a simplification. And consumers that want to do nice user-friendly simplification like gitk does can hang off the data stream. > it's also possible to update it when merging/pulling new data. If that's what you want to do, you can prototype it with a hook on fetch and commit. That is definitely an area that hasn't been explored - what nicer (but expensive) views on the history we have can be afforded by pre-computing things on fetch and commit hooks. cheers, m -- martin.langhoff@xxxxxxxxx martin@xxxxxxxxxx -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- 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
