You should still use "make current" - it works great on git-based FS repos. As for the core files, they are really only useful if you have exactly the same binary freeswitch file that created them. If you are not experiencing any seg faults then go ahead and delete them. If you are experiencing seg faults after updating to latest release then definitely open a JIRA ticket.<br>
<br>-MC<br><br><div class="gmail_quote">On Fri, Apr 9, 2010 at 2:33 PM, Lars Zeb <span dir="ltr"><<a href="mailto:larclap@yahoo.com">larclap@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US">
<div>
<p class="MsoNormal">Once we pull down the full FreeSWITCH version using git,
should we continue to use ‘make current’ to update thereafter?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I started with this command and interrupted it just after it
had pulled the source changes. I was surprised to see that “fs_cli”
no longer worked. I went to freeswitch/bin and it was gone. Are the contents of
this directory removed in ‘make current’?</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I also saw core files (core.pid?) in the freeswitch/bin
folder. Is it safe to remove these? They are about 200M each.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Thanks, Lars</p>
</div>
</div>
<br>_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br></blockquote></div><br>