Hi Chiradeep, I generate the patch using the normal git command:
git format-patch -s <last commit id on apache> Then I attach the diff file to a new request on Apache Review Board. Thanks -Radhika -----Original Message----- From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] Sent: Thursday, January 24, 2013 12:23 AM To: CloudStack DeveloperList Subject: Re: github workflow for non-committers Thanks Radhika. How do you generate the patches from your git workspace? How do you submit them to RB? On 1/23/13 4:37 AM, "Radhika Puthiyetath" <radhika.puthiyet...@citrix.com> wrote: >Hi Chiradeep, > >I have set up a Github space for the documentation at >https://github.com/radhikapc/incubator-cloudstack. > >The documentation is developed on Github prior to submitting the >patches on Review board. > >The changes are pulled in from Apache >(https://github.com/apache/incubator-cloudstack) every day, before I >push my changes to https://github.com/radhikapc/incubator-cloudstack. > >I have not created any branches for documentation, yet. > >Thanks >-Radhika > > >-----Original Message----- >From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com] >Sent: Tuesday, January 15, 2013 6:56 AM >To: CloudStack DeveloperList >Subject: github workflow for non-committers > >Folks who are not committers and are developing their features on github: >Care to share your workflow? Branching/testing/deployment/rebasing/etc > >I'm sure newcomers will be interested. >-- >Chiradeep
