Did the patch that fixes the mountain of maven warnings get missed?
> On Apr 26, 2018, at 11:52 PM, Akira Ajisaka wrote:
>
> + common-dev and mapreduce-dev
>
> On 2018/04/27 6:23, Owen O'Malley wrote:
>> As we discussed in hdfs-dev@hadoop, I did a force push to Hadoop's trunk to
>> replace the
owen, did you really, really have to do this? I have an large number of patches
against trunk and they are all now broken. Couldn't a rebase of the ozone tree
& a merge have worked?
> On 26 Apr 2018, at 22:23, Owen O'Malley wrote:
>
> As we discussed in hdfs-dev@hadoop, I did a force push to H
+ common-dev and mapreduce-dev
On 2018/04/27 6:23, Owen O'Malley wrote:
As we discussed in hdfs-dev@hadoop, I did a force push to Hadoop's trunk to
replace the Ozone merge with a rebase.
That means that you'll need to rebase your branches.
.. Owen
---
As we discussed in hdfs-dev@hadoop, I did a force push to Hadoop's trunk to
replace the Ozone merge with a rebase.
That means that you'll need to rebase your branches.
.. Owen
