Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Patrice Dumas via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: hassan hany <hassanhanyrashad@gmail.com>,
	Patrice Dumas <pertusus@free.fr>
Subject: [FFmpeg-devel] Re: [PATCH] doc/Makefile: add MAKEINFO variable
Date: Mon, 16 Feb 2026 20:08:29 +0100
Message-ID: <aZNrLfO7iJrSbil7@free.fr> (raw)
In-Reply-To: <CANzXe1M9ucshRJiPG2SQ+HLaf6bda3_pT0WkxkczDoJCp280og@mail.gmail.com>

On Mon, Feb 16, 2026 at 09:01:41PM +0200, hassan hany via ffmpeg-devel wrote:
> You should  submit the patch over at https://code.ffmpeg.org/ since that's
> where FFmpeg development happens nowadays

On https://code.ffmpeg.org/FFmpeg/FFmpeg, there is this, at the very
end:

 Contributing

 Patches should be submitted to the ffmpeg-devel mailing list using git format-patch or git send-email. Github pull requests should be avoided because they are not part of our review process and will be ignored.

Maybe this should be changed, if the process of submitting patches has
changed?

-- 
Pat
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

      reply	other threads:[~2026-02-16 19:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-03 21:06 [FFmpeg-devel] " Patrice Dumas via ffmpeg-devel
2026-01-10 22:05 ` [FFmpeg-devel] " Patrice Dumas via ffmpeg-devel
2026-02-16 18:08 ` Patrice Dumas via ffmpeg-devel
2026-02-16 19:01   ` hassan hany via ffmpeg-devel
2026-02-16 19:08     ` Patrice Dumas via ffmpeg-devel [this message]

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=aZNrLfO7iJrSbil7@free.fr \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=hassanhanyrashad@gmail.com \
    --cc=pertusus@free.fr \
    /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