[Bf-committers] Git issues and workarounds
gsr.b3d at infernal-iceberg.com
Tue Nov 26 21:11:39 CET 2013
sergey.vfx at gmail.com (2013-11-23 at 0329.22 +0600):
> If you're using `git add .` or `git commit .` stop doing this. Two reasons
> for this.
> First one is that this will stage changes to submodules and place them into
> commit (without notifying you about this is commit comments).
> Second one that AFAIR it'll add all untracked files to your commit.
> Including possible backup files, core dumps and so.
> Use `git commit -a` to include changes to all tracked files and take care
> of using `git add /path/to/specific/file` if you need to add new files to
> the repo.
"git commit -a" also should be avoided. It may not cause issues of the
same level than "git commit ." but it will keep on causing the issues
of a single commit changing unrelated things or even errors.
More information about the Bf-committers