For the first/initial patch, a diff against master attached to the issue would be fine. If the changes are reviewed and are acceptable, then you and we would look at back porting the changes to other branches, at which point in time helping us out with branch specific patches could be helpful.
On Mon, Aug 11, 2014 at 4:06 PM, Gomathivinayagam Muthuvinayagam < sankarm...@gmail.com> wrote: > Thank you, I am working on a jira ticket > https://issues.apache.org/jira/browse/HBASE-11699, and made a patch. I > would like to get it reviewed. > I submitted the patch by checking out the master, and made the changes > there, also I would like to make the patch for hbase 94.19 and 98.3, (as I > personally need them). So do I need to checkout each version, and then > commit there, and then submit a patch for each version? > Is that correct? > > Thanks & Regards, > > > > > On Mon, Aug 11, 2014 at 4:01 PM, Ted Yu <yuzhih...@gmail.com> wrote: > > > If you want to clone 0.98 branch, e.g., you can do: > > > > git clone -b 0.98 https://git-wip-us.apache.org/repos/asf/hbase.git > > <name-of-local-dir> > > > > master corresponds to 2.0 release > > 0.98 is the current stable release. > > > > Cheers > > > > > > On Mon, Aug 11, 2014 at 3:55 PM, Gomathivinayagam Muthuvinayagam < > > sankarm...@gmail.com> wrote: > > > > > I am trying to make few changes to the specific version of hbase. Is > > there > > > an easy way to checkout that from github? > > > > > > Also does master correspond to stable version? Is there any link that > > > describes about this? > > > > > > Thanks & Regards, > > > > > > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
