On Mon, Jan 27, 2020 at 5:58 PM Dave Marples <d...@marples.net> wrote:
> > On 10/01/2020 09:58, Alan Carvalho de Assis wrote: > > Hi Everyone, > > > > As told I opened an Infra ticket to fix sending .patch to dev@ list. > > > > That was the response I received: > > > > " [ > https://issues.apache.org/jira/browse/INFRA-19691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012638#comment-17012638 > > ] > > > > Sebb commented on INFRA-19691: > > ------------------------------ > > > > The content-type will depend on the mail client. > > > > I just tried with GMail, and it sent the file test.txt as > > Content-Type: text/plain; charset="US-ASCII"; name="test.txt" > > > > whereas test.patch resulted in: > > Content-Type: application/octet-stream; name="test.patch" > > > > == > > > > However, it's usually not ideal to send patches to mailing lists. > > Better to use an issue tracking system." > > > > Then he just Closed the ticket with the resolution: Information Provided > > > > BR, > > > > Alan > > So, will this be fixed or not? Tools are there to support users and > throwing away patches because the tools are sulky doesn't sound like > very support-y to me? > > Regards > > DAVE > Our workflow document already instructs users to send their patches with a .txt extension because of this issue. I just noticed that the git command given there doesn't correspond to that. I will fix that when I get to my computer soon. (I use 'git format-patch master --stdout > your_file_name_here.txt'; I don't know if there's another way that requires less typing.) That's all we can do on our end. It would take an act of Infra to change that. Nathan
