umm... no...<br><br>if you are doing the git equiv of an 'svn update' to the working copy all you will be doing is getting the most current code from the repository. <br><br>Think of it as an anonymous read-only checkout.<br>
<br><div class="gmail_quote">On Wed, Jul 9, 2008 at 1:36 PM, Matthew Nuzum <<a href="mailto:newz@bearfruit.org">newz@bearfruit.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wed, Jul 9, 2008 at 1:07 PM, Lathrop Preston <<a href="mailto:lathrop@prestonfam.org">lathrop@prestonfam.org</a>> wrote:<br>
> if you are doing updates to a static "working copy" there are no conflicts<br>
> to resolve.<br>
<br>
</div>If multiple people are doing updates to a static working copy there<br>
may be conflicts though.<br>
<div class="Ih2E3d">--<br>
Matthew Nuzum<br>
newz2000 on freenode<br>
_______________________________________________<br>
</div><div><div></div><div class="Wj3C7c">Cialug mailing list<br>
<a href="mailto:Cialug@cialug.org">Cialug@cialug.org</a><br>
<a href="http://cialug.org/mailman/listinfo/cialug" target="_blank">http://cialug.org/mailman/listinfo/cialug</a><br>
</div></div></blockquote></div><br>