Great, that works - it gives me the commit that Branch 1 was at at the time of cloning. One concern however. If I clone the repository, create Branch 2 to track Branch 1, and in the mean while push changes to the master branch of the repository, the commit that this command gives me changes (to the last commit that was pushed). The repository I am cloning from is bare, so in order to make changes to the master, I clone it again, make changes to the master branch of the clone and push those back (of course, this clone also has Branch 1 as a remote branch, but I am not making changes to it). What is git doing? Why does it change the commit history of Branch 1 when I did not push changes to it? Before pushing to master: $git log --oneline $(git merge-base origin/jateeq.2010-03-16.15-32 origin/master)..origin/master 610cfae added file.xml After pushing to master: $git log --oneline $(git merge-base origin/jateeq.2010-03-16.15-32 origin/master)..origin/master 9070a4d removed fcc.xml Thanks, Jawad -- View this message in context: http://n2.nabble.com/Getting-a-branch-s-time-of-creation-tp4750687p4751743.html Sent from the git mailing list archive at Nabble.com. -- 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