On Thu, May 19, 2016 at 9:46 AM, Aravinda <avish...@redhat.com> wrote:
> +1 for Prashanth's approach. > +1 > regards > Aravinda > > On 05/18/2016 03:55 PM, Kaushal M wrote: > > On Wed, May 18, 2016 at 3:29 PM, Humble Devassy > Chirammal<humble.deva...@gmail.com> <humble.deva...@gmail.com> wrote: > > > > On Wed, May 18, 2016 at 3:26 PM, Amye Scavarda <a...@redhat.com> > <a...@redhat.com> wrote: > > All in favor of the 'everyone working on this should clone again' > approach. > > Both approaches require cloning again, so which on are we voting for? > > 1. Prashanth's approach > - modify existing repo > - users re clone > - push force to their forks on github > > 2. Misc's approach > - create a new minified repo > - users clone/fork the new repo > > I don't mind either. > > > +2 on the same thought. :) > > _______________________________________________ > Gluster-devel mailing > listGluster-devel@gluster.orghttp://www.gluster.org/mailman/listinfo/gluster-devel > > _______________________________________________ > Gluster-devel mailing > listGluster-devel@gluster.orghttp://www.gluster.org/mailman/listinfo/gluster-devel > > > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-devel >
_______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
