A quick update on the status of 3.7.16.
I fell sick and couldn't do the release as scheduled on the 30th. I'll
try to get the release done over the next two days.
Neils, one of the changes you listed has a merge-conflict. I'll merge
the other two, only if you can confirm they are all independent
On Sun, Oct 02, 2016 at 04:39:35PM +0530, Kaushal M wrote:
...
> Neils, one of the changes you listed has a merge-conflict. I'll merge
> the other two, only if you can confirm they are all independent of
> each other.
> If you could confirm before this time tomorrow, I'll take them in.
Thanks! The
On Fri, Sep 30, 2016 at 8:50 PM, Ravishankar N
wrote:
> On 09/30/2016 06:38 PM, Niels de Vos wrote:
>
> On Fri, Sep 30, 2016 at 07:11:51AM +0530, Pranith Kumar Karampuri wrote:
>
> hi,
> At the moment 'Reviewed-by' tag comes only if a +1 is given on the
> final version of the patch. But for
On Mon, Oct 3, 2016 at 6:41 AM, Pranith Kumar Karampuri wrote:
>
>
> On Fri, Sep 30, 2016 at 8:50 PM, Ravishankar N
> wrote:
>
>> On 09/30/2016 06:38 PM, Niels de Vos wrote:
>>
>> On Fri, Sep 30, 2016 at 07:11:51AM +0530, Pranith Kumar Karampuri wrote:
>>
>> hi,
>> At the moment 'Reviewed-b
On 10/03/2016 06:58 AM, Pranith Kumar Karampuri wrote:
On Mon, Oct 3, 2016 at 6:41 AM, Pranith Kumar Karampuri
mailto:pkara...@redhat.com>> wrote:
On Fri, Sep 30, 2016 at 8:50 PM, Ravishankar N
mailto:ravishan...@redhat.com>> wrote:
On 09/30/2016 06:38 PM, Niels de Vos wro
On Mon, Oct 3, 2016 at 7:23 AM, Ravishankar N
wrote:
> On 10/03/2016 06:58 AM, Pranith Kumar Karampuri wrote:
>
>
>
> On Mon, Oct 3, 2016 at 6:41 AM, Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>>
>>
>> On Fri, Sep 30, 2016 at 8:50 PM, Ravishankar N
>> wrote:
>>
>>> On 09/30/2016 0
If you get credit for +1, shouldn't you also get credit for -1? It seems to me
that catching a fault is at least as valuable if not more so.
On October 3, 2016 3:58:32 AM GMT+02:00, Pranith Kumar Karampuri
wrote:
>On Mon, Oct 3, 2016 at 7:23 AM, Ravishankar N
>wrote:
>
>> On 10/03/2016 06:58
Hi,
The current add and remove brick commands aren't sufficient to support
add/remove brick on tiered volumes.So the commands need minor changes
like mentioning which tier we are doing the operation on. So in order
to specify the tier on which we are performing the changes, I thought
of using