Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Reto Kromer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Reto Kromer <lists@reto.ch>
Subject: Re: [FFmpeg-devel] [PATCH v6] gcc: Don't disable '-ftree-vectorize' if gcc version is 13 or newer
Date: Mon, 16 Jun 2025 10:28:37 +0200
Message-ID: <mailman.3330.1750062524.1384.ffmpeg-devel@ffmpeg.org> (raw)
In-Reply-To: <30d3b8b8-b496-99c3-f648-ca9ae24e9ae3@martin.st>

[-- Attachment #1: Type: message/rfc822, Size: 2663 bytes --]

From: Reto Kromer <lists@reto.ch>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v6] gcc: Don't disable '-ftree-vectorize' if gcc version is 13 or newer
Date: Mon, 16 Jun 2025 10:28:37 +0200
Message-ID: <0775c411-ecdc-4198-9ff1-dba4eafb3613@mail.infomaniak.com>

Martijn van Beurden wrote:

>So, there is a proposal to close the flac and flac-dev mailing

>lists.

>I'd like to know whether you would be willing to move over to

>GitHub discussions. GitHub would be the first choice because

>most discussions already happen there anyway.

+1

Kind regards from Reto


[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

  reply	other threads:[~2025-06-16  8:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-16  8:11 Martin Storsjö
2025-06-16  8:26 ` Martin Storsjö
2025-06-16  8:28   ` Reto Kromer via ffmpeg-devel [this message]
     [not found]   ` <0775c411-ecdc-4198-9ff1-dba4eafb3613@mail.infomaniak.com>
2025-06-16  8:29     ` Reto Kromer via ffmpeg-devel
2025-06-16  8:52       ` Kieran Kunhya via ffmpeg-devel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=mailman.3330.1750062524.1384.ffmpeg-devel@ffmpeg.org \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=lists@reto.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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