Hi Artem, I'm going to run the following commands to create the patch. are these steps correct ?
## Get the repo git clone -b ignite-sprint-5 https://github.com/apache/incubator-ignite.git git checkout -b ignite-788 ## Commit the changes git commit -a -m 'Ignite 788 Implementation'; git checkout -b ignite-sprint-5 git merge ignite-788 ## launch the script to create a file patch scripts/git-format-patch.sh Thank you, Regards, Gianfranco 2015-06-02 17:44 GMT+02:00 Artiom Shutak <[email protected]>: > Hi Atri, > > Now, we have useful information about patching here: > https://cwiki.apache.org/confluence/display/IGNITE/Sprint+Process. > But I agree with Cos, we need to have a page like "How to contribute". I > will do it. > > Atri, thanks, for your feed back. You should be on branch with your > changes. I will add more understandable information at the script. > > > -- Artem -- > > On Tue, Jun 2, 2015 at 6:28 PM, Konstantin Boudnik <[email protected]> wrote: > > > In Bigtop we follow this process > > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute > > > > which is quite handy as it turned out. > > > > Cos > > > > On Tue, Jun 02, 2015 at 08:38PM, Atri Sharma wrote: > > > Folks, > > > > > > Is git diff > patch.patch good enough to be put on JIRA? I tried > running > > > format script but got following errors (I am on sprint 5 branch): > > > > > > > > > Already on 'ignite-sprint-5' > > > Your branch is ahead of 'origin/ignite-sprint-5' by 1 commit. > > > Switched to a new branch 'tmppatch' > > > (nothing to squash)Already up-to-date. > > > # On branch tmppatch > > > > > > > > > and it generates an empty patch file. > > > > > > > > > -- > > > Regards, > > > > > > Atri > > > *l'apprenant* > > >
