Re: Merging GlusterD changes for 3.7.1

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

 



Several of the changes have now been merged on master. When the changes have been backported to 3.7, please add them to the etherpad. We'll be looking at it for changes to be merged once the moratorium is removed.

On 28-May-2015 12:18, "Krishnan Parthasarathi" <kparthas@xxxxxxxxxx> wrote:

> be merged and needs our attention, add them back to the etherpad at the END!
> Don't forget to add one of us as a reviewer, it helps with some sanity checks
> I could perform on this data set ;) Feel free to ask if anything is not
> clear.

Please add a 'keyword' by which you would like to indicate your patch's primary
component/feature. For e.g, if it's a patch needed for bitrot feature, then add "bitrot"
with a _space_ after your review URL. Please be consistent with naming. i.e, don't
add bitrot and Bitrot for different patches. It's perfectly fine to not add a
'keyword'.

Complete example,

http://review.gluster.org/10936 bitrot

cheers,
kp

> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel@xxxxxxxxxxx
> http://www.gluster.org/mailman/listinfo/gluster-devel
>
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
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