Hi, I just noticed that the following commits virtually erased all the code history, and they made it way harder to use git for analysis of the changes.
I would suggest stopping further commits to the branch that contains "clearing all + updating all" changes, and start over from a reasonable branch. Please, take this seriously. It is really crucial to keep git annotate in a good shape, otherwise bug analysis becomes extremely hard. 0affa12bb12e45bf681a6e6a918d68884d7e1877 "clearing all the project contents from the xalanj master branch" 356ce496faa80d97ae8a8406e37f6bd994b39233 "updating master branch, to have same contents as the branch xalan-j_2_7_1_maint" For instance, if you check "git blame" for DocumentCall.java, you'll find that "every line was added only 2 months ago": https://github.com/apache/xalan-java/blame/master/src/org/apache/xalan/xsltc/compiler/DocumentCall.java I am afraid the above commits are showstopper for further activity on the branch. git blame on xalan-j_2_7_1_maint branch looks much better: https://github.com/apache/xalan-java/blame/xalan-j_2_7_1_maint/src/org/apache/xalan/xsltc/compiler/DocumentCall.java Since there were no releases on the master branch since the bad commits, I would suggest removing the commits from the repository completely. It is fine from the ASF policies, and it would be great to kill the commits as having commits that modify 400'000 lines make Git history hard to browse in various tools. --- If you want to "forget everything on master and continue with xalan-j_2_7_1_maint", then the best scenario would be retargeting main branch to xalan-j_2_7_1_maint and continuing from there. --- Dear xalan committers, please, consider using pull requests for proposing the changes. I am sure a pull request that performed 403,833 deletions and 400,423 additions would raise an eyebrow. Vladimir
