On Nov 27, 2008 at 17:58, Henning Westerholt <henning.westerholt(a)1und1.de> wrote: It's ok, you didn't do anything wrong :-) No, there isn't any problem, the commit is on your trie_mods branch not on master. You see the commit message because of the email script we use and not because a mistake in the merge. The email script tries to send mail only for new commits, but if it doesn't find anything new (like in this case), it sends the top of the branch commit anyway as a failsafe (it doesn't have special support for detecting newly created branches). You should read this message as: henning/trie_mods created with head == displayed commit :-) We might extends the mail script in the future to send a better message in cases as above if people find the current behaviour too confusing (but for now I consider this quite low priority). For now our email script does not support: - new branch created messages - non fast forward updates of a branch - branch deletion For all of the above a commit message with the current head of the branch will be sent (for the delete it would be the old branch head and the branch name will have DELETED appended to it). Should I make the script public somewhere? Is anybody interesting in extending it? Andrei

On Nov 28, 2008 at 11:24, Henning Westerholt <henning.westerholt(a)1und1.de> wrote: [...] It's more about perl skills and testing it (e.g. on the test repo). The script already detects new branches and deleted branches, it just not sends a different message. There is only a send_commit_notice() function and we would need a send_new_branch_notice() and a send_del_notice() or more params to send_commit_notice(). Andrei