Yes, +1 to handle it case by case with proper reminders. Rui Wang <amaliu...@apache.org> 于2020年10月30日周五 上午6:19写道：
> >People who write to dev@ list and attach the stacktrace as an image don't > >really know if the list accepts images or not. > >Making images forbidden does not help to teach people to > >attach stacktraces as text. > > I guess the way will be when we see those cases, we reply to ask to replace > the image by text. This is not perfect :( but I guess that is what will > happen. > > > -Rui > > On Thu, Oct 29, 2020 at 4:19 AM Vladimir Sitnikov < > sitnikov.vladi...@gmail.com> wrote: > > > To all who vote for "disallow images", > > Do you think it really helps if the images are forbidden? > > > > People who write to dev@ list and attach the stacktrace as an image > don't > > really know if the list accepts images or not. > > Making images forbidden does not help to teach people to > > attach stacktraces as text. > > > > We don't want to use MS Word with a screenshot inside to share a > > stacktrace. > > I believe that is obvious. We don't need a discussion about that, do we? > > > > --- > > > > How are you going to share diagrams (e.g. GraphViz-based charts)? > > How are you going to share memory leak suspects? > > > > There are cases when a screenshot makes a lot of sense. > > For instance, memory dump can easily contain sensitive information, so > > memory dump can't be shared. > > However, a screenshot might be helpful, so a screenshot with leak > suspects > > would be more than welcome. > > > > Vladimir > > >
