On 14/12/2013 09:51, Quoth Vicente J. Botet Escriba:
Le 13/12/13 09:16, Gavin Lambert a écrit :
By default, pull and merge in git will auto-commit if they don't see any conflicts. You can tell them not to by using --no-commit. I don't see the file changes in https://github.com/boostorg/chrono/commits/develop.
The auto-commit is to your own local repository, not the origin remote. You have to push the commits upstream to make them public. The way that status/diff/log/commit etc work in git is a bit different than in SVN, partly due to philosophical differences and partly out of necessity as a distributed VCS. You should probably read some tutorials. Also you might want to consider using a GUI front-end (eg. TortoiseGit, on Windows) -- while this does hide some of the plumbing (which you sometimes need to know) it's often an easier way to get used to the behaviour and to visualise changes.