On Tue, 25 Apr 2006, sean wrote: > > It's no different for a bug tracker or other 3rd party software that wants > to interface with git, it's bad design to force them to parse a single > free form text comment into individual pieces to extract their meta data. > Especially when git could easily add the ability to add multple comments > to each commit. Git _does_ make that easy. It's called the "tree". It's where you add any arbitrary files to a commit. The point here is that core git should do one thing, and one thing only. You can then build up any policy you want on top of that. But in order for core git to be stable, it has to have nice rules about what it cares about, and what it does not. And the rule is: git cares about the commit header, but not about the free-form. Which means that anything it doesn't care about, it goes into the free-form section, not into some "X-header" section. Whatever you build on TOP of git can have its own rules in that free-form section. For example, the kernel project has this "X-header" thing called the "sign-off", and git itself picked it up. There's even some support to add it automatically to commits (the same way we add the "revert" info automatically to commits), but nobody claims that git should "parse" that information, or that it should be part of the "header". Linus - : 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