From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Regarding Git Tooling
Date: Tue, 21 Jan 2025 08:17:39 +0100
Message-ID: <Z49KE1qCKw1dUlh5@phare.normalesup.org> (raw)
In-Reply-To: <20250121023804.GE4991@pb2>
Michael Niedermayer (12025-01-21):
> The contributor looks in MAINTAINERS and sees if there is a preferred place to
> submit a patch(set) to.
What if the patch series affects areas handled by multiple maintainers?
What if the patch would benefit from the expertise of another developer
than the maintainer?
Having two systems in parallel in practice does not allow anybody to use
only the one they like: in practice it forces everybody to use both.
That is terrible.
Regards,
--
Nicolas George
_______________________________________________
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".
next prev parent reply other threads:[~2025-01-21 7:17 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 20:39 Marth64
2025-01-20 21:09 ` Nicolas George
2025-01-20 21:12 ` Marth64
2025-01-20 22:25 ` Nicolas George
2025-01-20 22:44 ` Marth64
2025-01-20 23:28 ` Marth64
2025-01-22 12:39 ` Nicolas George
2025-01-27 20:39 ` Jan Ekström
2025-01-27 20:55 ` Timo Rothenpieler
2025-01-20 22:44 ` compn
2025-01-20 22:14 ` Leo Izen
2025-01-21 1:26 ` Michael Niedermayer
2025-01-21 1:56 ` Soft Works
2025-01-21 2:38 ` Michael Niedermayer
2025-01-21 3:22 ` Soft Works
2025-01-21 3:56 ` Kieran Kunhya via ffmpeg-devel
2025-01-21 4:03 ` Soft Works
2025-01-21 4:07 ` Marth64
2025-01-21 7:17 ` Nicolas George [this message]
2025-01-21 1:57 ` compn
2025-01-21 2:41 ` Michael Niedermayer
2025-01-21 2:56 ` James Almer
2025-01-21 3:34 ` Soft Works
2025-01-21 11:51 ` Niklas Haas
2025-01-21 17:55 ` Frank Plowman
2025-01-21 18:20 ` Niklas Haas
2025-01-21 12:04 ` Niklas Haas
2025-01-21 15:39 ` Lynne
2025-01-21 15:54 ` Michael Niedermayer
2025-01-21 16:14 ` Soft Works
2025-01-22 0:38 ` Soft Works
2025-01-22 1:08 ` Marth64
2025-01-22 2:00 ` Soft Works
2025-01-22 6:41 ` martin schitter
2025-01-25 7:54 ` Soft Works
2025-01-25 19:17 ` martin schitter
2025-01-25 22:20 ` Marth64
2025-01-21 16:22 ` James Almer
2025-01-21 17:48 ` Michael Niedermayer
2025-01-21 17:57 ` James Almer
2025-01-21 18:14 ` Niklas Haas
2025-01-25 6:57 ` Rémi Denis-Courmont
2025-01-21 16:37 ` James Almer
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=Z49KE1qCKw1dUlh5@phare.normalesup.org \
--to=george@nsup.org \
--cc=ffmpeg-devel@ffmpeg.org \
/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