From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/4] doc/developer.texi: extend the argument for submitting patches
Date: Mon, 14 Nov 2022 17:40:10 +0100
Message-ID: <Y3JvajHgJ7GtW7ad@phare.normalesup.org> (raw)
In-Reply-To: <DM8P223MB036593DC993795DFDFFE140FBA059@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
Soft Works (12022-11-14):
> What are your points? Which are your objections? Please show the
> code that you think is wrong and say how it should be done instead.
For the record, I have, multiple times.
--
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:[~2022-11-14 16:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 9:13 [FFmpeg-devel] [PATCH 1/4] doc/developer.texi: improve the introductory text Anton Khirnov
2022-11-14 9:13 ` [FFmpeg-devel] [PATCH 2/4] doc/developer.texi: extend the argument for submitting patches Anton Khirnov
2022-11-14 9:35 ` Soft Works
2022-11-14 9:53 ` Anton Khirnov
2022-11-14 10:46 ` Soft Works
2022-11-14 11:07 ` Anton Khirnov
2022-11-14 11:20 ` Soft Works
2022-11-14 11:40 ` Soft Works
2022-11-14 12:42 ` Nicolas George
2022-11-14 14:34 ` Anton Khirnov
2022-11-14 15:13 ` Soft Works
2022-11-14 15:18 ` Paul B Mahol
2022-11-14 15:39 ` Soft Works
2022-11-14 15:45 ` Soft Works
2022-11-14 16:13 ` Anton Khirnov
2022-11-14 16:38 ` Soft Works
2022-11-14 16:40 ` Nicolas George [this message]
2022-11-14 17:25 ` Soft Works
2022-11-14 17:47 ` Nicolas George
2022-11-14 22:05 ` Michael Niedermayer
2022-11-14 22:49 ` Soft Works
2022-11-14 9:13 ` [FFmpeg-devel] [PATCH 3/4] doc/developer.texi: demote the "contributing" chapter to a section Anton Khirnov
2022-11-14 9:13 ` [FFmpeg-devel] [PATCH 4/4] doc/developer.texi: refine the "contributing code" section Anton Khirnov
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=Y3JvajHgJ7GtW7ad@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