stanio commented on PR #103: URL: https://github.com/apache/xalan-java/pull/103#issuecomment-1766925534
> Merge hashes have changed; odd but OK. Not sure which merge hashes you're referring to but as I've pointed out in the PR description: > * Two superfluous merge commits were dropped I didn't do it intentionally but it is a consequence of the cherry-pick. > Two commits seem to have vanished: > > ``` > be0d250e committing minor changes to xalanj README file, as per the following change that was done earlier : movement of the 2.7.3_release test cases to jira directory. also making a minor improvement to error handling within xalanj implementation codebase, when variables were not been resolved within an xslt 1.0 stylesheet. > 690bd044 Merge pull request #5 from jkesselm/master > ``` As I've pointed out, the merge commit is gone, yes. It has been unnecessary, anyway. The first one you could see in your previous `git log` output – just with a different hash. Again, this is a result of the cherry-pick. The same commit applied to a different parent will have a different hash. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
