I would think doing automatic updates (ie cron) to a working copy under backup would take care of this issue.<br><br>am i missing something?<br><br><div class="gmail_quote">On Wed, Jul 9, 2008 at 11:05 AM, Colin Burnett <<a href="mailto:cmlburnett@gmail.com">cmlburnett@gmail.com</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;">I'll jump straight to my question: any solutions for using git in a<br>
structured environment? git was intentionally designed to be<br>
distributed (I believe this was Linus' #1 requirement) and it does<br>
that well. However, this means there are immediate problems when<br>
wanting to use this in a structured environment (likewise trying to<br>
CVS/SVN in a distributed manner) when you want a copy of all code on a<br>
designated machine (notably for backup purposes). That can surely be<br>
achieved by pushing changes to the backup server but seems wide open<br>
to forgetting to do so.<br>
<br>
Does anyone use git in a structured environment or know/seen/read of<br>
any solutions?<br>
<br>
<br>
Colin<br>
_______________________________________________<br>
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>
</blockquote></div><br>