Jun 11 2018
Jun 10 2018
@Yaron_Koren I don't think there is a problem with the present code. However, the author of the issue( @redrooster ) mentioned that he already fixed it locally. The present format looks better to me rather than "YYYY/MM". So, how about abandoning this patchset and closing the issue?