Hi, all I also have no strong opinion though, it seems it'd be better to keep as much activities (that is, commit logs) as possible there. I'm afraid few activity logs possibly make newbies misunderstand that hivemall is inactive.
As for the rebasing, it's not tough to rebase #285 (this is my own pr). So, rewriting the logs sounds good to me. // maropu On Tue, Nov 29, 2016 at 11:24 PM, Makoto Yui <[email protected]> wrote: > Kai, > > 2016-11-29 22:35 GMT+09:00 Kai Sasaki <[email protected]>: > > Currently we have 6 PRs and some of them (especially #285, #336 and #385) > > are relatively large. > > It might cause somewhat troublesome rebasing. > > Yes, it's my concern. > > But, such large PRs should better to be contributed in the Apache > Incubation process. > I'm considering to invite some of them to the Hivemall committer. > > Another concern is moving github stars/watchers as seen in [1]. > [1] https://issues.apache.org/jira/browse/INFRA-12995 > > > Do you think some of them are not ready to be merged? I think merging > some > > of them before reflogging history > > can make migrating work easy. But if they are not ready, it's okay. We > can > > work on rebasing after this work. > > I'm currently reviewing #385 but it need to be revised in several parts. > Also, #336 requires large refactoring. > > So, better to do initial code dump first. > > Shallow copied repository can be pushed from git v1.9 and later > (I'm not sure about ASF git version though). > http://blogs.atlassian.com/2014/05/handle-big-repositories-git/ > > Thanks, > Makoto > -- --- Takeshi Yamamuro
