Hello, Just a small announcement of a little project I just published. Normally I wouldn't bother troubling you all, but I thought whoever it was wrote the key feature (git-notes) might appreciate knowing it was being used... I've been wanting for a while to keep my blog in git (in fact I did do so, except it was a full ikiwiki installation, but ikiwiki is so slow, and meant I had to use my own computer to host my blog). What I wanted was to have a post-receive hook that automatically compiled the markdown-syntax source files to HTML articles and posted them to my blogger account. However, I wanted to be able to modify, rename, delete, etc, etc the local files while keeping the remote end in sync. I was motivated to write the necessary script when I noticed that git 1.7 comes with shiny git-notes support. This is just what I needed -- when you post an article to blogger using the GData API, it gives you back a freshly assigned post ID. That post ID is the only (reliable) way you have of keeping track of the link between the remote article and the local file that generated it. My script grabs that ID and uses git-notes to store it against the object hash of the original article file. Then, when you change that article in the repository (git diff-tree is a godsend by the way), it's a simply matter of using git-notes again to look up the postID and send the appropriate GData command to update that article. Summary: git-notes... excellent, exactly the tool I needed. If you write a blog and would prefer git + markdown for maintaining it over HTML in a web interface, the repository is at http://gitorious.org/git_blogger Andy -- Dr Andy Parkins andyparkins@xxxxxxxxx -- 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