Well, if you can't have any custom modules, there's no need to have VCS access to the code, right?<div><br></div><div>At least, that's the line of reasoning that I'd expect from a client that was trying to tell me what modules to use.<br clear="all">
--<br>Cameron Eagans<br><a href="http://cweagans.net" target="_blank">http://cweagans.net</a><br>
<br><br><div class="gmail_quote">On Mon, Aug 20, 2012 at 2:39 PM, Greg Knaddison <span dir="ltr"><<a href="mailto:greg.knaddison@acquia.com" target="_blank">greg.knaddison@acquia.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, Aug 20, 2012 at 9:58 PM, Cameron Eagans <<a href="mailto:cweagans@gmail.com">cweagans@gmail.com</a>> wrote:<br>
> Plus, I assume that this is going to mean that you can't have a version<br>
> controlled copy of the site and you're just going to have to work on a<br>
> shared dev site (with all of the other developers on the project). This is<br>
> going to be a huge pain in the neck.<br>
<br>
Where did this assumption come from?<br>
<br>
Regards,<br>
Greg<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
consulting mailing list<br>
<a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
</div></div></blockquote></div><br></div>