On Mon, 30 Jul 2007, Jeff King wrote: > > If you followed a strict policy of always merging topics to a "base" > branch as your first parent, then never allowing fast forwards should > allow a very easy-to-read history in gitk. Only if only *one* person ever does any merges. Immediately when you have other people merging code, you're now back in the same boat. This is why I personally think the whole policy of "no fast forward" is totally broken. It's only usable in a non-distributed environment, where there is one central person who does everythng (a so-called "star topology"). Linus - 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
