Re: Avoid merge conflicts for per component eventing changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Tue, Aug 30, 2016 at 4:05 PM, Atin Mukherjee <amukherj@xxxxxxxxxx> wrote:
Is it a good idea to consolidate all of the events declaration (the identified ones) in one patch and then respective patches take care of implementing them to avoid the merge conflicts we are going through?

I've sent a patch [1] for the same and if all the per component event patches can be made dependent of it, merge conflicts will go away.

[1] http://review.gluster.org/#/c/15351
 

--Atin



--

--Atin
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux