From nobody Sun Apr 13 10:28:51 2025 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Zb69J6Tq5z5t5v2 for ; Sun, 13 Apr 2025 10:29:24 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (prime256v1) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "E5" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Zb69J3bJNz4Ncb for ; Sun, 13 Apr 2025 10:29:24 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@FreeBSD.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1744540156; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=EVBxJsyYqtZ/8308n70H8NrqaRJFyH2p41DnJZH6BOs=; b=awaUiPyEVIqQVznGhDSpELHJ2rqUhQud5D6sDHRU6OkPDYpuDpyXPX+VEiz5K6StpIanjo MF+TtLOuVq7lh2PNQCqCpsaTGxB2Dd6L854Dj8P0DRDjTJdMU8psIBaD9S/7xQhPbn7TJ+ qTCRiWDhgQPpoeSPrjyAvG4e6zMLTAbeYKFq6/enXHUV/9iR5O8Dh8e6IrwEnkcT1uawfW q6JdxRE41BXnYE7sFMalS2trVTKN8caivw0Yjtg7KtuPmGaHMz1EDSNm2YQ/WKGsenB6Y7 aEvsgagg152atBOdO2GxNtRfd42ItzSecIi16gti2iuam2tgJXzw8s8Yr/1//g== Date: Sun, 13 Apr 2025 12:28:51 +0200 From: Alexander Leidinger To: Artem Bunichev Cc: Tomoaki AOKI , freebsd-hackers@freebsd.org Subject: Re: Forgotten MFC In-Reply-To: <20250412134658.e41004e25df0044a6f5498e6@bk.ru> References: <20250411204934.d574639172d393183ace4749@bk.ru> <20250412040913.9fc4944e0cf6142e086f4bad@dec.sakura.ne.jp> <20250412134658.e41004e25df0044a6f5498e6@bk.ru> Message-ID: Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_36c9ad75e40431cf3656803c689481c2"; micalg=pgp-sha256 X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:89.238.64.0/18, country:DE] X-Rspamd-Queue-Id: 4Zb69J3bJNz4Ncb X-Spamd-Bar: ---- This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_36c9ad75e40431cf3656803c689481c2 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2025-04-12 12:46, schrieb Artem Bunichev: >> Me, too, not a developer, but you need to specify which commit you >> mean >> to get answers from developer. > > Sure, here is a commit: > https://cgit.freebsd.org/src/commit/?id=272b4b764bdfb563f655da37ef9ec8c01c77f386 > > But I would say that I was interested in general approach for MFC'ing, > rather > than a particular case. What I mean is how do developers keep track of > which > commits should be MFC in, say, 14-STABLE, because as I can see, not all > of the > commits in -CURRENT branch include "MFC after:" field. There is some code which tracks commits and looks for "MFC after:". It emails the developer when the time has passed. Nothing else will happen in an automated way, no reminder, nothing. Everything else is up to the developer. Source: https://github.com/freebsd/mfctracker Website: https://mfc.freebsd.org/ Regarding how a developer decides when to put a MFC marker or not, is up to them. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_36c9ad75e40431cf3656803c689481c2 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmf7kfMACgkQEg2wmwP4 2IYv/Q//WQCdzVyA9Y6zJyxVXaY/i4IMu7oOBmLG+aYzTKwMd6L4r4zk2D+JzoJ2 6/y4DOLAizO17skAQ2LNKFAhDu3U6GfGYMmbXiweIbZDQoOFEMMN4z9QQU4KtV1V ocvhOmS6h57keePbD/BkkaOb9j+hePn9MgdkmLTNJOifSHylFqGe/+e6KAbFmDSJ UDDtF+WimAd1KrDNUibpy4InK7+7LRWygkgrpge+7gL5N+UOfIzMA1ogzDnjoIkq YjKP7i8wgMELKEVnxWMjiHQQIv1U9Y9SB8XEvUKtb7fppg6ZzqByfawAgpLNEYxz xTGgzWOQZL/V1DVynSSPqCzJBZir4o7EDvN5iSxcvg5mh4TEjiEPlDPk+UprGRC+ AWDbagFOzpSIgysnbq9XhmAqclj+vAbTUOCL/P8crJ2Et/C5DX/1xl8ASXMb/uip DeykUuZp4OzYtvITqXDTVh8ZVDbnJuOGnJjrjAfOxV2CLo6dSNhqRXRFGaYzoyCk rQTTupmCV34e8OwGC1+2gErBAfuK34bqguxSicYNKgsV/OygHwA/THTDdXnezoCh qfLrmeDOOm6+rHiHiTzgo7FggVyjXe1gaFPDxbXGuJD6Jvc5joW8hE1Mwjwq2KvE Xtkn/IBEB38XzxxcWO6r5CvsNbb+8cDPty5HP1+TpD0cCZsAVA8= =vHm4 -----END PGP SIGNATURE----- --=_36c9ad75e40431cf3656803c689481c2--