Re: [Gluster-Maintainers] [release-3.7] Tag v3.7.17 doesn't actually exist in the branch

On Fri, Nov 18, 2016 at 1:17 PM, Kaushal M wrote: > IMPORTANT: Till this is fixed please stop merging changes into release-3.7 > > I made a mistake. > > When tagging v3.7.17, I noticed that the release-notes at 8b95eba were > not correct. > So I corrected it with a new

[Gluster-Maintainers] [release-3.7] Tag v3.7.17 doesn't actually exist in the branch

IMPORTANT: Till this is fixed please stop merging changes into release-3.7 I made a mistake. When tagging v3.7.17, I noticed that the release-notes at 8b95eba were not correct. So I corrected it with a new commit, c11131f, directly on top of my local release-3.7 branch (I'm sorry that I didn't

[Gluster-Maintainers] Build failed in Jenkins: regression-test-burn-in #2088

See Changes: [Kaleb S. KEITHLEY] ganesha/scripts : use export id for dbus signals -- [...truncated 9487 lines...] ok 164, LINENUM:330 ok 165, LINENUM:333 ok 166, LINENUM:334 ok 167,

[Gluster-Maintainers] Jenkins build is back to normal : regression-test-burn-in #2083

See ___ maintainers mailing list maintainers@gluster.org http://www.gluster.org/mailman/listinfo/maintainers