From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 3C81F42CDC for ; Tue, 3 May 2022 15:53:18 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id AF74268B2D8; Tue, 3 May 2022 18:53:16 +0300 (EEST) Received: from mail-qt1-f170.google.com (mail-qt1-f170.google.com [209.85.160.170]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id E9D5E6806F5 for ; Tue, 3 May 2022 18:53:10 +0300 (EEST) Received: by mail-qt1-f170.google.com with SMTP id hh4so13739022qtb.10 for ; Tue, 03 May 2022 08:53:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=syy4sAOd46/v837wuWIhC69Uw1NNydjuZzay/o/EJ9o=; b=Fgzrc1Ri2vitl8KlEDuE6eSoFIB/M3kpr7XL/XNtGl6DHVifBd5zMyKhXkipm7XQiO Cjqtm5Cp+WxpsNs7S1QGU9wtmBuhCj1SfJ3ooSRXwrqK7Yr2UoFqWLj3chISH/7zrky/ nd9/nj0+ppZx8bcnM/t17t7aSSfcUeNvecbHnTqwUcSs/FUQjozj93iIELiibZJqh9N8 X0pg5BebTVrRi6x3OzQEfwjC554oFyZcsBReXdArTHgq7mppHgLHuFE2FovCkmkD9qRi sQ63mJ2eiJqsFIiFEJ02JvM+IiVEwr5rozl4bN4UFNP6uGAXNtrJdhDGf1AXmxuFNtUZ cQ/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=syy4sAOd46/v837wuWIhC69Uw1NNydjuZzay/o/EJ9o=; b=STVEQ4+TRE6SDRdkHxI6mlV1ibwCZRWDEEau/MeEprCF9oONaTJrBBHWZpSufRbe0R vY1MSZEMqUUjI7em5Kmb3WOmTK2g29JhCYrRJOdIUx58khAnDmZHbpc+4TNHvx7vVNo0 UPzDP4nede9PPk4xoubud8YyEhSPS2iO+nx0JLewbMZv6f+7NRW7X9vZsRZ4UCRkFRKE DGT10mTZFQfpy+5dQhUK5yvlUkqvcfWnGnsd+tG+eWXR1wiY472sXK8CJ3nm5mBDSR8F W95xi3kBXXIgJUIcsmC15clM3NMHnktfDw3vGPei3RumJmkKCZuaFnZyYPWXPZdG+rFm gTjg== X-Gm-Message-State: AOAM5314ZlTqcX579QudlPpSFbkZGHF0DCyhbQYblEOCMlHDONFBRDIf ykMf0Z/NrH16TgyQK5IuaLM3a+poV/8= X-Google-Smtp-Source: ABdhPJzgDMtlU5JCGXHJaS0oqSR7tDzu6CmBb+/EsjrnkwOVLN5Z4fPu0lVKgeUfkOMJgQARCjXjUg== X-Received: by 2002:a05:622a:206:b0:2f3:b1de:9a70 with SMTP id b6-20020a05622a020600b002f3b1de9a70mr1902284qtx.397.1651593189555; Tue, 03 May 2022 08:53:09 -0700 (PDT) Received: from [192.168.1.35] (c-68-41-54-207.hsd1.mi.comcast.net. [68.41.54.207]) by smtp.gmail.com with ESMTPSA id r17-20020a37a811000000b0069fc13ce24dsm6148907qke.126.2022.05.03.08.53.09 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 03 May 2022 08:53:09 -0700 (PDT) Message-ID: <8ed34ddb-313e-7492-c921-789095b88f51@gmail.com> Date: Tue, 3 May 2022 11:53:08 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Content-Language: en-US-large To: ffmpeg-devel@ffmpeg.org References: From: Leo Izen In-Reply-To: Subject: Re: [FFmpeg-devel] Need help submitting a patch X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: 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".