Prior to this change, git status would report untracked files of the
following sort if run during a build:
?? src/rpcprotocol.o-e628def3
These files should be explicitly ignored not only because they are a
nuisance, but given that they appear and disappear quickly, they may be
inadvertently added to the index even if one has been careful to check for
untracked files with git status prior to a git add ..
Prior to this change, `git status` would report untracked files of the
following sort if run during a build:
?? src/rpcprotocol.o-e628def3
These files should be explicitly ignored not only because they are a
nuisance, but given that they appear and disappear quickly, they may be
inadvertently added to the index even if one has been careful to check
for untracked files with `git status` prior to a `git add .`.
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/7b95c7be8ddcaefa4e13d717b9abb9b2a8c6cc21 for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
Who generates these .o files with a hex code in them?
This is the default behavior for me on OS X. Standard XCode setup, gcc 4.2.1. Note that the files are transient, only in existence while the target .o file in question is being created. Makes for an odd experience when running git status while a build is running in a separate terminal.
On Mar 25, 2014, at 10:06 AM, Wladimir J. van der Laan notifications@github.com wrote:
Who generates these .o files with a hex code in them?
— Reply to this email directly or view it on GitHub.
If only we supported out-of-tree building...
Anyway, ACK
ACK (If my opinion counts for anything.)