On Thu, 10 May 2007, Johan Herland wrote: > > BTW, I'm wondering whether anybody has ever thought about allowing > after-the-fact annotations on commits. Kinda like free-form > continuations on the commit message. It would allow people to make > notes on previous commits that were either forgotten at commit-time, or > only became apparent after the commit was done. We kind of have some of that. Tag objects can be used that way, and the "grafts" file is a very special case. But if you want to do it on a larger scale, you'd need something that is really optimized for that. For example, git internally now has a notion of "decorating" arbitrary objects with arbitrary data, and if you just had an efficient file format to create such decorations (for blame or other special ops), the *code* is easy to write. It's how git log --decorate works right now (the "data" is just the tag names, but you could make it read other decorations, and the git data structures are very efficient, and allow different types of decorations to be used independently of each other). 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
