Ramkumar Ramachandra wrote: > This is like API documentation- should it go into the commit message? > Maybe put this in a a dedicated repo_tree.txt like trp.h? Good question. The answer depends on whether we want to keep it maintained. Since this is not meant to be a general-purpose API, I thought it simplest to document it in the commit message and let future commit messages describe the purpose of future changes. We are not approaching any limit on the length of a commit object, after all. Jonathan -- 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