From nobody Wed Jan 3 23:27:17 2024 X-Original-To: freebsd-current@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 4T55V66VRJz56xBL for ; Wed, 3 Jan 2024 23:27:26 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T55V64GMfz4mnF; Wed, 3 Jan 2024 23:27:26 +0000 (UTC) (envelope-from steffen@sdaoden.eu) Authentication-Results: mx1.freebsd.org; none Date: Thu, 04 Jan 2024 00:27:17 +0100 Author: Steffen Nurpmeso From: Steffen Nurpmeso To: Bakul Shah Cc: Brooks Davis , Jamie Landeg-Jones , FreeBSD Current , yuri@freebsd.org Subject: Re: git repo port issues? Message-ID: <20240103232717.CAc7Sxai@steffen%sdaoden.eu> In-Reply-To: <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> Mail-Followup-To: Bakul Shah , Brooks Davis , Jamie Landeg-Jones , FreeBSD Current , yuri@freebsd.org User-Agent: s-nail v14.9.24-585-g9999e323b6 OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4T55V64GMfz4mnF X-Spamd-Bar: ---- 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:15987, ipnet:217.144.128.0/20, country:DE] Bakul Shah wrote in <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org>: |On Jan 3, 2024, at 11:22=E2=80=AFAM, Brooks Davis wr= ote: |>=20 |> Nothing about dates is centralized in git, but some server side checks |> could be implemented on CommitDate. IMO we should require that |> CommitDate be >=3D the previous one and less than "now". | |Given that git commit objects form a DAG, I don't see how you can |impose linearity. On the other hand, if a project agrees, and for example locks the main branch, any merging or plain committing to it can enforce commit-amending including date-updates etc, as well as expanding $CVS and @# SCCS format strings (i think by then this discussion came up in the past, and Warner Losh rejected such a thing, if i recall correctly ... but may not). --End of <46C8698A-A004-4B5F-9107-6D9FD3685074@iitbombay.org> --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)