Re: [Gluster-devel] trash.t failure

I've reverted the original patch entirely. Our policy is to either mark the test as bad or revert the entire patch. This seems to have caused multiple failures in the test system, so I've reverted the entire patch. Please re-land the patch with any fixes as a fresh review. On Wed, Apr 18, 2018 at

Re: [Gluster-devel] Regression with brick multiplex on demand

Super useful. Thanks Nigel (and Amar for the idea). On Tue, Apr 17, 2018 at 12:04 PM, Nigel Babu wrote: > Hello folks, > > In the past if you had a patch that was fixing a brick multiplex failure, > you couldn't test whether it actually fixed brick multiplex failures >

[Gluster-devel] Coverity covscan for 2018-04-17-b2f94254 (master branch)

GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-04-17-b2f94254 ___ Gluster-devel mailing list Gluster-devel@gluster.org

Re: [Gluster-devel] Agenda for Maintainer's meeting tomorrow (18th April).

Please note that This meeting involves 2 big topics related to developers/community, please try to attend the meeting. 1. Coding style (which can be very personal for many developers, great to agree and move forward on this). 2. GPL cure discussions - The link given explains most of it. But if

[Gluster-devel] Agenda for Maintainer's meeting tomorrow (18th April).

Meeting date: 14/18/2018 (April 18th, 2018), 19:30 IST, 14:00 UTC, 10:00 EDT BJ Link - Bridge: https://bluejeans.com/205933580 - Download: Attendance -

[Gluster-devel] Fwd: [Gluster-infra] [Bug 1564149] Agree upon a coding standard, and automate check for this in smoke

All, Can we have more attention to this bug and provide inputs from your experience in different project? This would save us lot of time in reviewing, and also make sure our contributors are sending code which is uniform regardless of their editor settings. Expectation is, we come up with an

[Gluster-devel] Regression with brick multiplex on demand

Hello folks, In the past if you had a patch that was fixing a brick multiplex failure, you couldn't test whether it actually fixed brick multiplex failures easily. You had two options: * Create a new review where you turn on brick multiplex via the code and also apply your patch. Mark a -1 for