[FFmpeg-devel] Maintaining email threads for patch submissions using git send-email

[Allan Cady]

Could someone please have a look at an issue I'm having in resubmitting a patch, trying to get the resubmission email to appear as a reply on an existing thread? In order to conform to submission guidelines in ffmpeg-devel, I'm using git format-patch and git send-email, using the --in-reply-to option, but it's not giving the expected results.

I had started a thread in this mailing list for a patch I've been working on. I had gotten some comments to my initial submission, worked on addressing them, and last night I submitted it again. I wanted the resubmission to appear as a reply on the earlier thread, to preserve that conversation. After configuring git to use the same email account that I had used for the earlier submissions and comments, I used the following git command:

    git send-email --to=ffmpeg-devel at ffmpeg.org --in-reply-to="e4d3f14f-ac69-9424-804e-ee5025059eff at passwd.hu" <patch-file-name>

I got the message ID from the following line in the message I wanted to reply to:
Message-ID: <e4d3f14f-ac69-9424-804e-ee5025059eff at passwd.hu>

But when I submitted the patch, it showed up in the list as a reply on a completely different, unrelated thread. 

So I came back and fixed a couple other issues in the patch (I had messed up the subject line), double-checked that I had copied the Message-ID, and entered this command (adding angle brackets this time to the ID, just in case that might matter). 

    git send-email --to=ffmpeg-devel at ffmpeg.org --in-reply-to="<e4d3f14f-ac69-9424-804e-ee5025059eff at passwd.hu>" <patch-file-name>

Still, the message went to the same incorrect thread.

Is there possibly something else I need to add to the send-email command to get it to attach to the older thread?

Thanks,

Allan