From nobody Wed Jan 3 19:22:35 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 4T503l09Vdz56WqC for ; Wed, 3 Jan 2024 19:22:43 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (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 4T503k544tz4GLj; Wed, 3 Jan 2024 19:22:42 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Authentication-Results: mx1.freebsd.org; none Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 48FF53C019A; Wed, 3 Jan 2024 19:22:35 +0000 (UTC) Date: Wed, 3 Jan 2024 19:22:35 +0000 From: Brooks Davis To: Jamie Landeg-Jones Cc: freebsd-current@freebsd.org, yuri@freebsd.org Subject: Re: git repo port issues? Message-ID: References: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> 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=us-ascii Content-Disposition: inline In-Reply-To: <202401031913.403JDZBt028036@donotpassgo.dyslexicfish.net> X-Rspamd-Queue-Id: 4T503k544tz4GLj 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:36236, ipnet:199.48.128.0/22, country:US] On Wed, Jan 03, 2024 at 07:13:35PM +0000, Jamie Landeg-Jones wrote: > https://cgit.freebsd.org/ports/ > > The latest update to "main" is : > > author Yuri Victorovich 2023-01-03 14:49:38 +0000 > committer Yuri Victorovich 2023-01-03 14:49:38 +0000 > > I.e. A year old. Reading the commit message, it does appear to be a wrong > clock, rather than an old message, but whilst the author date is local to > the author, I thought the commit date was centralised. > > If nothing else, this does seem to bugger up "commits since " > within git itself. Nothing about dates is centralized in git, but some server side checks could be implemented on CommitDate. IMO we should require that CommitDate be >= the previous one and less than "now". -- Brooks