Hi Vladimir, On Sat, Jul 1, 2023 at 1:48 PM Vladimir Sitnikov <sitnikov.vladi...@gmail.com> wrote:
> The same issue impacts xalan-j_xslt3.0 branch. > > Would you please fix git history before commiting more changes to the > impacted branches? I personally don't think, this issue is currently impacting anything related to XalanJ project. Perhaps, some of the source code history, with which you seem to be concerned with (as per git scm sense) has been affected while we merged XalanJ 2.7.3 repos codebase to the XalanJ 'master' branch. This could be technically possible to be improved, but I don't see substantial benefits of doing this task around these days. Lots of, XalanJ source code history is still available, on the 'master' branch, and that seems to me to be, useful and enough to take the XalanJ project for further enhancement. But if you still feel that, this issue is important and needs to be fixed, I'd suggest to please raise a XalanJ jira issue for this possibly with issue type 'Improvement' and mentioning pros and cons of doing this task, and then that could be tracked and decided appropriately by XalanJ team. -- Regards, Mukul Gandhi --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
