Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
* [FFmpeg-devel] Maintaining email threads for patch submissions using git send-email
       [not found] <1589751619.1637820.1710179084519.ref@mail.yahoo.com>
@ 2024-03-11 17:44 ` Allan Cady via ffmpeg-devel
  2024-03-11 17:47   ` James Almer
  0 siblings, 1 reply; 2+ messages in thread
From: Allan Cady via ffmpeg-devel @ 2024-03-11 17:44 UTC (permalink / raw)
  To: FFmpeg Development Discussions and Patches; +Cc: 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@ffmpeg.org --in-reply-to="e4d3f14f-ac69-9424-804e-ee5025059eff@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@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@ffmpeg.org --in-reply-to="<e4d3f14f-ac69-9424-804e-ee5025059eff@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


_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [FFmpeg-devel] Maintaining email threads for patch submissions using git send-email
  2024-03-11 17:44 ` [FFmpeg-devel] Maintaining email threads for patch submissions using git send-email Allan Cady via ffmpeg-devel
@ 2024-03-11 17:47   ` James Almer
  0 siblings, 0 replies; 2+ messages in thread
From: James Almer @ 2024-03-11 17:47 UTC (permalink / raw)
  To: ffmpeg-devel

On 3/11/2024 2:44 PM, Allan Cady via ffmpeg-devel wrote:
> 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@ffmpeg.org --in-reply-to="e4d3f14f-ac69-9424-804e-ee5025059eff@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@passwd.hu>
> 
> But when I submitted the patch, it showed up in the list as a reply on a completely different, unrelated thread.

They at least show up in my client as replies alright.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-03-11 17:47 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <1589751619.1637820.1710179084519.ref@mail.yahoo.com>
2024-03-11 17:44 ` [FFmpeg-devel] Maintaining email threads for patch submissions using git send-email Allan Cady via ffmpeg-devel
2024-03-11 17:47   ` James Almer

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git