From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Need help submitting a patch
Date: Tue, 3 May 2022 15:31:17 +0200
Message-ID: <YnEupQcAaD9wMtYg@phare.normalesup.org> (raw)
In-Reply-To: <CAJBzVsmw-F6OLFL5tkxEmwL6UenRMbgByTdnFQYbTMhsr_rvLA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 760 bytes --]
Traian Coza (12022-05-03):
> Thanks. I'll use the ffstaging/FFmpeg repo. I didn't know about that, it
> seems much simpler.
It is not supported by the core of the project.
> I've tried using -n (n= number of commits), but it only
> generates n emails, I only want 1.
Look at how other people submit patches: several commits means several
mails.
> The source.err file seems to be empty, however. Should I be concerned about
> this? It seems to do with the fact that I've added some files.
Yes, you need to fix it.
> On Tue, May 3, 2022 at 3:54 AM Nicolas George <george@nsup.org> wrote:
Top-posting is strictly forbidden on this mailing-list. If you do not
know what it means, look it up.
Regards,
--
Nicolas George
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- 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".
next prev parent reply other threads:[~2022-05-03 13:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 4:12 Traian Coza
2022-05-03 4:27 ` Soft Works
2022-05-03 7:54 ` Nicolas George
2022-05-03 13:27 ` Traian Coza
2022-05-03 13:31 ` Andreas Rheinhardt
2022-05-03 13:33 ` Andreas Rheinhardt
2022-05-03 13:31 ` Nicolas George [this message]
2022-05-03 14:08 ` Soft Works
2022-05-03 14:21 ` Traian Coza
2022-05-03 14:22 ` Traian Coza
2022-05-03 14:35 ` Nicolas George
2022-05-03 15:36 ` Traian Coza
2022-05-03 15:43 ` Soft Works
2022-05-03 15:50 ` Traian Coza
2022-05-03 15:53 ` Leo Izen
2022-05-03 16:17 ` Traian Coza
2022-05-03 17:02 ` Leo Izen
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=YnEupQcAaD9wMtYg@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