[Bf-committers] Git issues and workarounds
gsr.b3d at infernal-iceberg.com
Tue Nov 26 22:25:11 CET 2013
sergey.vfx at gmail.com (2013-11-27 at 0239.37 +0600):
> > "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.
> I never had issues with using -a. And for now doing `git commit -a` COULD
> cause issues meanshile `git commit .` DOES give issues on every call from
> the working dir root.
Was 50fbebe0 done with "git commit -a"? That explains 780459e4. ;) It
was just cosmetic, but other errors can be compile breaking (half
edited files with true syntax errors, eg), and in any case, using
something like git, there is no reason for such noise.
There is a need to "change gears" and use the tools with more
precision. There are status, diff, log, --amend, "squash"... to check
and solve issues before pushing.
More information about the Bf-committers