[ Nit-picking. Not really important. But I reacted to a part of Jakub's explanation ] On Thu, 14 Jun 2007, Jakub Narebski wrote: > > > And is it intended that (clean) merges are shown? > > Path limiting simplifies history, and might linearize it (i.e. merges > become non-merges). Actually, path limiting, when it simplifies merges, will *only* simplify a merge when one of the parents was identical to the end result (which implies that the other parents were obviously not interesting as far as the end result is concerned!). But that has a secondary effect: such a merge will then (by definition) always be simplified away, since the simplified merge no longer makes any changes to the set of files in question! So "merges become non-merges" is not really true (except in a very internal sense that will be invisible to the outside). They either stay as merges (end result is different from any of the parents on their own), or they go away entirely (end result is identical to one of the parents and the merge ends up not containing any change atr all). This explanation may, of course, be more nit-picking than anybody really wanted to hear. 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
