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 ED65742E49 for ; Mon, 8 Aug 2022 19:27:02 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 997EC68B76F; Mon, 8 Aug 2022 22:26:59 +0300 (EEST) Received: from w4.tutanota.de (w4.tutanota.de [81.3.6.165]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id BF33F68B6D1 for ; Mon, 8 Aug 2022 22:26:53 +0300 (EEST) Received: from w3.tutanota.de (unknown [192.168.1.164]) by w4.tutanota.de (Postfix) with ESMTP id F22311060344 for ; Mon, 8 Aug 2022 19:26:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1659986812; s=s1; d=lynne.ee; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender; bh=GYKyMiH46lBFimSOdomR+haGG4tUqKF9muHB6BEL00w=; b=Nl53uXa0jyp4PqsP2Eq1x5YHWyD3Qk6clkJ4bCwzTFc/nx2Zy8GW4buJ4NKmAs6W eaCUSLYlKrUVrMa4Eyka38RUMxfDlcwUt8HK1BlinoOgXfZURgeHKn6xWCUWHgDRH/R NXhw5hcgfuJ7CyaPyWMt2HCkivD50vpI3S84kTrBc0SD7yf1VOQCQ1Gd5DiJ+y+lvF+ wBY6InuX1R8juNn9Y27ZdWeTSO4LUIjXhCKdd+VED+4vgU+ZscBhqZPvqL4kBXM/oWd EZl4wHF10L5GqAISswdfjHeBkIlvApDiwAQNYag/H3sGc6t0zNjcaM2zWgMQSDIitaF 7NqhytY3iQ== Date: Mon, 8 Aug 2022 21:26:52 +0200 (CEST) From: Lynne To: FFmpeg development discussions and patches Message-ID: In-Reply-To: <20220808145008.26162-1-michael@niedermayer.cc-N8xvyjN----2> References: <20220808145008.26162-1-michael@niedermayer.cc> <20220808145008.26162-1-michael@niedermayer.cc-N8xvyjN----2> MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [RFC] git and signing commits and tags 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-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Aug 8, 2022, 16:50 by michael@niedermayer.cc: > Given the recent server issues, i wonder if we should suggest/recommand > and document signing commits and tags > > i tried to push such commit to github and it nicely says "verified" > https://github.com/michaelni/FFmpeg/commit/75f196acd16fb0c0ca7a94f0c66072e7c6f736bf > > Ive generated a new gpg key for this experiment as i dont have my > main key on the box used for git development and also using more > modern eliptic curve stuff (smaller keys & sigs) > i will upload this key to the keyservers in case it becomes the > one i use for git. > I sign all of my commits, I think it should be recommended but not required. One downside is that you can sign commits from others with your own key (for instance when pushing a patch from someone along with your commits, and signing all at once via rebase), which can be misleading, so it takes some work to reorder commits or push them in stages so this doesn't happen. It makes sense that it's the committer who's signing it, but git or github don't make a distinction when it comes to signing. _______________________________________________ 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".