From: Romain Beauxis <romain.beauxis@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Recommendations to facilitation patch reviews on forgejo/ML?
Date: Fri, 1 Aug 2025 18:17:54 -0500
Message-ID: <CABWZ6ORtXt+6C4fLz_PJH0atvOq9RSRdbc7tRxMcMU=dqXrTMQ@mail.gmail.com> (raw)
In-Reply-To: <aIlClBu7-cspwyYw@phare.normalesup.org>
Le mar. 29 juil. 2025 à 16:52, Nicolas George <george@nsup.org> a écrit :
>
> Romain Beauxis (HE12025-07-29):
> > Are there any recommendations on how to best get attention to some
> > patches/changes?
>
> Speaking for myself, I will not lift a finger to adapt to this thing
> until the dust is settles and the promises that were made about a full
> ability to interact by mail and command-lie are met, including specific
> documentation.
>
> And if a patch is pushed that affects the areas I am responsible of
> without me seeing it, I reserve the right to revert on the spot.
Part of my question is: how should people know what are the area you
are responsible for and who to contact when working on specific areas?
I would imagine the MAINTAINERS file and, in this case, it's a great
thing that you are actually available but that's not the case for
other areas.
> 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".
_______________________________________________
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-08-01 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 21:42 Romain Beauxis
2025-07-29 21:52 ` Nicolas George
2025-08-01 23:17 ` Romain Beauxis [this message]
2025-08-02 9:59 ` Nicolas George
2025-07-31 11:12 ` Rémi Denis-Courmont
2025-08-01 23:19 ` Romain Beauxis
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='CABWZ6ORtXt+6C4fLz_PJH0atvOq9RSRdbc7tRxMcMU=dqXrTMQ@mail.gmail.com' \
--to=romain.beauxis@gmail.com \
--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