You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@freemarker.apache.org by GitBox <gi...@apache.org> on 2020/04/16 07:31:31 UTC

[GitHub] [freemarker] ddekany commented on issue #63: 2.3.29 maintenance

ddekany commented on issue #63: 2.3.29 maintenance
URL: https://github.com/apache/freemarker/pull/63#issuecomment-614467635
 
 
   What I meant is that using `classic_compatible` in 2020 is already a quite special need (or I hope so), and then, using that, but not expecting exactly the classic behavior is even more so. So, why are you using `classic_compatible`?

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services