On 10 September 2010 07:58, Moises Silva <moises.silva@gmail.com> wrote:
Something is wrong in your box. That file is not committed.
Hmm. Curious, looks like git had me confused: brian@aquitard:~/freeswitch$ git status # On branch master nothing to commit (working directory clean) brian@aquitard:~/freeswitch$ ls -l ./libs/freetdm/Makefile.in ls: cannot access ./libs/freetdm/Makefile.in: No such file or directory brian@aquitard:~/freeswitch$ echo hello > ./libs/freetdm/Makefile.in brian@aquitard:~/freeswitch$ git diff ./libs/freetdm/Makefile.in brian@aquitard:~/freeswitch$ I expected to see either (a) an error or (b) a diff representing a new file, but got an empty diff instead. Is there any reliable way of finding out if a file is committed or not under git? -- Brian May <brian@microcomaustralia.com.au>