00:32 <xue> hi, i know it isnt help channel but i don't know if it is a but or am i dumb

00:33 <xue> https://pastebin.com/yTJG04uD

00:34 <xue> the mp3 adding metadata breaks if '-codec copy' option is present

00:35 <xue> it drops first character, 'f' from some lines, not even every other, just some

00:36 <xue> and i end up with 'Error opening input file ile:///home/xue/Music/Filename.mp3.' error

00:44 <dank074> Hello. I am struggling with sending a patch without using `git send-email` since it is complicated to set up. I followed the instructions in the docs for submitting patches and generated an eml file with the command `git format-patch -s -o "outputfolder" --add-header "X-Unsent: 1" --suffix .eml --to ffmpeg-devel@ffmpeg.org -1 HEAD`

00:44 <dank074> However, Patchwork still doesn't show my patch, which probably means my patch is still getting rejected

00:44 <dank074> Any help is appreciated

00:44 <xue> nvm my previous messages

00:44 <xue> https://ffmpeg.org/pipermail/ffmpeg-user/2014-May/021179.html

01:05 <BtbN> you need to be subscribed to the list to send messages

01:10 <kierank> dank074: I would just do git format-patch HEAD~1

01:10 <kierank> and send it as an attachment

01:10 <BtbN> that'd still fail the same way in that case though

01:11 <kierank> I wonder what "X-Unsent: 1" does

01:11 <kierank> and why people have to do custom smtp headers

01:11 <BtbN> it tells the mail client it's a draft iirc

01:12 <BtbN> it won't be sent with that in the headers

01:23 <dank074> The command with those headers are what is suggested in the docs

01:23 <dank074> But yes, I was not subscribed to the mailing list. Let me do that and try again. Thanks

01:23 <kierank> so sorry you have to deal with this BS workflow

01:36 <dank074> Patch finally reached Patchworks (thanks for the guidance), but now it looks like there's a problem with it: https://patchwork.ffmpeg.org/project/ffmpeg/patch/caef2cbb-06ca-4820-95bd-fd954bd0be25@gmail.com/

01:37 <dank074> Did I do something wrong? again, this is the command I used: git format-patch -s -o "outputfolder" --add-header "X-Unsent: 1" --suffix .eml --to ffmpeg-devel@ffmpeg.org -1 HEAD

01:40 <kierank> not sure

01:40 <dank074> It's a very simple, 1 line change. If someone can submit it then that will be great. I have no idea what I am doing wrong

01:46 <BtbN> just send it as attachment. gmail mangled up the patch

01:59 <dank074> Do I just disregard the previous email and just send a new one with the same subject?

02:00 <dank074> Sorry about all these questions, this is my first time submitting changes via email

02:00 <kierank> yeah

02:02 <dank074> Ok, and just to verify, docs state: "send patches as base64-encoded attachments, so your patch is not trashed during transmission". Is this still the case, or can I send the patch in plaintext?

03:47 <Compn> dank074, plaintext is fine

03:48 <Compn> been a while since i saw a patch fail , but sometimes it happens...