Hi Guys, I wrote a script to clone the repos, and activate the hooks. Thought it may be useful to others.
It just saves time messing around every time you want to checkout a clean repo. As default all the hooks are set to true, you can set the ones you don't want as false at the top of the script, Use ./clone_dc.sh (-a -c -d) to clone the aggregator, core, docs repo respectively Cheers Martyn ----- Original Message ----- From: "Jason Guiditta" <[email protected]> To: [email protected] Sent: Tuesday, May 11, 2010 10:04:23 PM GMT +00:00 GMT Britain, Ireland, Portugal Subject: Re: [deltacloud-devel] Git config/patch standards for developers A link might be handy, eh? http://deltacloud.org/page/Git_config On Tue, May 11, 2010 at 4:51 PM, Jason Guiditta < [email protected] > wrote: Hello all, We have had some issues with inconsistency in the setup of people's git configuration (whitespace sneaking in, for example), so I thought I would try to put together a page with examples of how things should be set up, as well as some guidelines for patch submittal. I don't expect I have covered everything, so feel free to add points that did not cross my mind for this first pass, or make a correction if you see a mistake. If any new developer has questions on how to start submitting patches, I would like to be able to direct them to this as our canonical guideline doc. Patches that apply cleanly, are clearly for one repo or another, and have useful descriptions are much more pleasant to review. This also increases the likelihood of said review happening. Thank you for your time. </soapbox> -j _______________________________________________ deltacloud-devel mailing list [email protected] https://fedorahosted.org/mailman/listinfo/deltacloud-devel
clone_dc.sh
Description: application/shellscript
_______________________________________________ deltacloud-devel mailing list [email protected] https://fedorahosted.org/mailman/listinfo/deltacloud-devel
