# gitster@xxxxxxxxx / 2014-09-12 10:31:30 -0700: > Roman Neuhauser <neuhauser@xxxxxxxxxx> writes: > > git-diff-tree without --root is absolutely silent for the root commit, > > and i see no bad effects of --root on non-root commits. are there any > > hidden gotchas? IOW, why is the --root behavior not the default? > > Because tools that was written before you proposed that change > expect to see nothing for the root commit, and then you are suddenly > breaking their expectations? i'm not proposing anything, i'm just curious why it is this way. my line of thinking: there must be (or have been) a grave reason to break the simple consistency, or the current behavior must be very useful for something and i'm just missing what it is. the reasons for the behavior may have been invalidated by further developments, or it may have been a wrong decision we're stuck with for BC; i'm just curious about history. motivation for my question is that i'm scripting git-diff-tree and i need it to produce the diff for root commits as well. i like my scripts as simple as possible, so i'd like to use --root *always*. is it safe? -- roman -- 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