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 4EF604B91B for ; Wed, 19 Jun 2024 11:22:20 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id B9F1568D66B; Wed, 19 Jun 2024 14:22:17 +0300 (EEST) Received: from relay8-d.mail.gandi.net (relay8-d.mail.gandi.net [217.70.183.201]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id E2D3C68D260 for ; Wed, 19 Jun 2024 14:22:10 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id 1277C1BF203 for ; Wed, 19 Jun 2024 11:22:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1718796130; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ocfQFjh1iG8TjAfMg26Q9sgDjqoUjeDftjKew0j90Tk=; b=QCY2TVs3fp+ZN60464ci4SMi6OfCVFzTzVhNVC3HqMzoGGWfTK5PlM/UOdqJIFUOBP4r2t p/75rBderOvqcOXkFuswvT/DV0Cvxi1qn7Ui+taZIRPz3vSUIHqac61bM8amaJ1gaEiZCs 5XPMreWyxrvyjnDuDh1cTCRIjgWOif1TlfK8hB0dccd4EkkK2hF+cCzguLsQd9nn8fMZI0 Fpi641nPILUfr3Q8SidpSkg8r+eJfFxq4Eqqhlu/L9Pw4mktUCkvm51kAGWrSWLkuABHcK gUAixJJuscn3aMcVKLhe3+bnlIwVjzrTgVuSq7Ucez1V3iC2t5w6kGeRGSObPg== Date: Wed, 19 Jun 2024 13:22:09 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240619112209.GQ4991@pb2> References: <20240616230831.912377-1-michael@niedermayer.cc> <20240616230831.912377-7-michael@niedermayer.cc> <171860804339.28895.10807353542433656746@lain.khirnov.net> <20240617234825.GE4991@pb2> <171870537407.28895.5960894387853799090@lain.khirnov.net> MIME-Version: 1.0 In-Reply-To: <171870537407.28895.5960894387853799090@lain.khirnov.net> X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [PATCH 7/9] MAINTAINERS: Update the entries for the release maintainer for FFmpeg 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: multipart/mixed; boundary="===============3352317426183583403==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============3352317426183583403== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dUqh8vgUBVXHzm9w" Content-Disposition: inline --dUqh8vgUBVXHzm9w Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 18, 2024 at 12:09:34PM +0200, Anton Khirnov wrote: > Quoting Michael Niedermayer (2024-06-18 01:48:25) > > On Mon, Jun 17, 2024 at 09:07:23AM +0200, Anton Khirnov wrote: > > > Quoting Michael Niedermayer (2024-06-17 01:08:29) > > > > Ive been told that someone at the BCN video tech meetup claimed to = be the > > > > "release maintainer for FFmpeg". > > > >=20 > > > > If you have any doubt who maintains releases, just do something lik= e the following and look at the output: > > > > VER=3D5.1 > > > > echo commiters ; git shortlog --group=3Dcommitter -s n$VER..relea= se/$VER -n ;\ > > > > echo authors ; git shortlog -s n$VER..release= /$VER -n > > >=20 > > > Passive aggressive gossip does not belong in a commit message. > >=20 > > we generally explain in a commit message the "why" and "what" and so on. > > There was no intention of any aggression. >=20 > The commit message is indirectly accusing an unindentified person of > trying to usurp your position as a release maintainer. The accusation is > aggressive, and the fact that it is indirect makes it passive > aggressive. >=20 > Not providing any specifics beyond "someone said that someone said" > makes it gossip. >=20 > Each of those factors in isolation IMO makes this text inappropriate for > a commit message. I dont entirely agree but ill drop it from the commit message. [...] > > The example git commands simply show the authors and commiters on the r= elease branch > > since the first release on it. I think its reasonable to provide these = as reference >=20 > I don't. Nobody is disputing your role as a release maintainer. Its always nice to learn that iam A release maintainer and not THE release = maintainer. :) Which releases are maintained by someone else ? And who is that someone else ? Can that other release maintainer look at some of the regressions we have? IIRC there are cases that since the multithreding dont 100% of the time produce the same output, it makes testing more difficult. And while already at that subject can that other release maintainer help marking regressions as such and as release blocking ? So they are more vissible and can get fixed. thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Concerning the gods, I have no means of knowing whether they exist or not or of what sort they may be, because of the obscurity of the subject, and the brevity of human life -- Protagoras --dUqh8vgUBVXHzm9w Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZnK/XQAKCRBhHseHBAsP qyf/AJ9nXTXYu8bpTI+fXVFH7+owb6XeNgCdF+O/eeVgy/9NxIyu3X18n8u9V18= =jOK5 -----END PGP SIGNATURE----- --dUqh8vgUBVXHzm9w-- --===============3352317426183583403== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============3352317426183583403==--