From: Traian Coza <traian.coza@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Need help submitting a patch
Date: Tue, 3 May 2022 12:17:22 -0400
Message-ID: <CAJBzVsmVSrNbJcdYC=0KFLDP-0x=MT==DsVqpqCN-VM7uz+6Zg@mail.gmail.com> (raw)
In-Reply-To: <8ed34ddb-313e-7492-c921-789095b88f51@gmail.com>
Thanks, I finally managed to submit my patch with your instructions.
However, I see that the "Less secure apps" setting will no longer be
available in a month. What do you plan on doing then? (I see you also use
gmail)
On Tue, May 3, 2022 at 11:53 AM Leo Izen <leo.izen@gmail.com> wrote:
> On 5/3/22 00:12, Traian Coza wrote:
> > Hi! I am new to contributing to FFmpeg, and I have a technical question.
> >
> > I'm trying to submit a patch, but it's a fairly large patch, which I've
> > made in multiple commits. I don't know how to generate the email for this
> > patch. The example command given on the website (with format-patch) only
> > generates the email for a single commit. I've searched the web and I
> don't
> > really see an easy way to do it. Can someone help me out with this?
> >
> I find the easiest way to do it for me is to generate the patches with
> "git format-patch" and then send them with "git send-email".
>
> Once you have your patches atop the master branch, you can create a
> directory called outgoing/ and then run something like:
>
> git format-patch -M -o outgoing/ --cover-letter origin/master
>
> In this case, --cover-letter generates a cover letter, which you then
> edit to give a short blurb of what your patch set looks like. Then when
> you run git send-email outgoing/* you will have the patches embedded as
> replies to that cover letter email. "origin/master" is the hash of the
> last commit *before* yours, but it can by any ref, such as
> origin/master, not just a commit hash. You can also just substitute the
> commit hash there if your repositories/branches are named differently.
>
> Since you use Gmail (at least, from your email address), you will need
> to enable Less Secure Apps if you have two-factor authentication
> disabled. If you have it enabled, you will have to generate an App
> Password for git-send-email, and then use that as the account password
> instead of your own.
>
> - Leo Izen (thebombzen)
>
>
> _______________________________________________
> 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:[~2022-05-03 16:17 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
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 [this message]
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='CAJBzVsmVSrNbJcdYC=0KFLDP-0x=MT==DsVqpqCN-VM7uz+6Zg@mail.gmail.com' \
--to=traian.coza@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