<div class="gmail_quote">On Thu, Sep 9, 2010 at 7:38 PM, Brian May <span dir="ltr"><<a href="mailto:brian@microcomaustralia.com.au">brian@microcomaustralia.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On 10 September 2010 07:58, Moises Silva <<a href="mailto:moises.silva@gmail.com">moises.silva@gmail.com</a>> wrote:<br>
> Something is wrong in your box. That file is not committed.<br>
<br>
Hmm. Curious, looks like git had me confused:<br>
<br>
brian@aquitard:~/freeswitch$ git status<br>
# On branch master<br>
nothing to commit (working directory clean)<br>
brian@aquitard:~/freeswitch$ ls -l ./libs/freetdm/Makefile.in<br>
ls: cannot access ./libs/freetdm/Makefile.in: No such file or directory<br>
brian@aquitard:~/freeswitch$ echo hello > ./libs/freetdm/Makefile.in<br>
brian@aquitard:~/freeswitch$ git diff ./libs/freetdm/Makefile.in<br>
brian@aquitard:~/freeswitch$<br>
<br>
I expected to see either (a) an error or (b) a diff representing a new<br>
file, but got an empty diff instead.<br>
<br>
Is there any reliable way of finding out if a file is committed or not<br>
under git?<br>
</blockquote><div><br></div><div>From the top FreeSWITCH directory:</div><div><br></div><div><div>git ls-files libs/freetdm/Makefile.in</div><div><br></div><div>If there is no output, means is not tracked. You can add --error-unmatch if you want to see an error on files that are not tracked.</div>
<div><br></div><div>git ls-files libs/freetdm/Makefile.in --error-unmatch</div><div><br></div><div><br class="Apple-interchange-newline">Moises Silva<br>Senior Software Engineer<br>Sangoma Technologies Inc. | NEW 100 Renfrew Drive, Suite 100, Markham ON L3R 9R6 Canada<br>
t. 1 905 474 1990 x128 | e. <a href="mailto:moy@sangoma.com" target="_blank">moy@sangoma.com</a></div><br><br></div></div>