Thank you for your answer. After my message this morning, that's what I did: I commited with the mock data then tag. Tonight, I just tried something which do exactly what I wanted to do this morning: $ git checkout -b temp $ git commit -a -m 'My config file with mock_data=true' $ git tag -a v0.1 -m v0.1 $ git checkout master $ git branch -D temp With these commands, the tag is associated to a commit which is not in any branch. Regards, ©om Le vendredi 24 février 2012 à 20:27 +0100, Zbigniew Jędrzejewski-Szmek a écrit : > On 02/24/2012 11:24 AM, Romain Vimont (®om) wrote: > > $ git log --pretty=online > > 0ef41513d0b6d0ad28f21d0ac1da7096ad1dc6ff This is the last commit > > a4702c69c28484d357179166cf3b116764da20a4 This is a commit > > > > Now, I edit some files (for example in a config file "mock_data=true"), > > then I want to tag without commiting this change. > > > > $ git tag -a v0.1 -m 'My v0.1 with mock data' > > > And it shows the diff between a4702c69c28484d357179166cf3b116764da20a4 > > and 0ef41513d0b6d0ad28f21d0ac1da7096ad1dc6ff (the two last commits). > > Hi Romain, > git tag attaches the tag to the last commit, 0ef41513 in your case. > Dirty changes in your tree are ignored by the tag command. You would > have to commit them first, and attach the tag to this new commit. > > zbyszek > -- 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