On 01 May 2013, at 16:03, Nathan England <[email protected]> wrote: > We really don't want to change our setup because of some rigid quality > control that > must be done, so that really is out of the question. How do we make git work > best > for our setup? Do we really need to change? Is there a better way for our > review > process by the QA team? (who are *not* coders at all, btw) > I do not really see a need to change. On many projects I am the only developer. Yet I use git, if for no other reasons than having a backup and being able to revert. Having this setup in place already, it makes it exceedingly easy to allow someone else to clone the code and start helping. I would suggest that you just start using git. As you use it, the benefits will become apparent as will different avenues for making it work for your setup.
/* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
