On 03/17/2016 10:57 AM, Malahal Naineni wrote: > 1. If you want, I can replace 2.3.0-1 with 2.3.1 version and can move your > tag to point to that 2.3.1 (just one commit changing the CMAKE file). > Then I will rebase my patches that I did today on top of that and name > it 2.3.2. > > 2. My back ported today's patches are very minor, so if you don't care what > V2.3.1 tag points to, we make move the tag to current checked in 2.3.1. > > 3. If you don't want to change any history at this point, I will change > the current HEAD with 2.3.2 (instead of 2.3.1) and tag it as V2.3.2. > > Let me know which option (#1, #2 or #3) you like. All of them need > trivial changes, so doing any of those is no big deal. #1 or #2 make it > very clean, but #3 leaves V2.3.1 tag pointing to V2.3.0-1 (looks odd, > that is all). >
I had started packaging a 2.3.1 in Fedora and EPEL based on V2.3.1 tag/release -- the bad one. I think I can abort that. Not exactly sure what the implications are wrt having another, different nfs-ganesha-2.3.1.tar.gz are. I guess I'll find out. ;-) -- Kaleb ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ Nfs-ganesha-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
