Not exactly. There are indeed changes in the files since we use an attribute filter to modify the file ( smudge action of the filter). The clean action of the filter however clean the file to restore it to its original state ( as in the repository) so basically we have a modification notification ( which is correct ) but we get an error when commiting the file since there are no changes to commit.
I do realise it is a bit strange as setup though. I use the info on the substition on commit/checkout http://git-scm.com/book/ch7-2.html -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
